Your design is just too tightly coupled and will not pass if i do the review

Also i can sense some sort of a mild spaghetti code from it.
both framework and code access the a library? what will happen if you change library to use? what will happen if Library will change its interfaces or parameters? you need to modify both your CODE and framework? too bad of a design.
i think it is better to have atleast an adapter (design patterns) from your code to a certain library, for you know... flexibility and to avoid tight coupling, this prevents your code from being too over dependent in a certain library.
With an adapter, you can always change and adapt different library but your code will be unmodified.
and entry point to any library should be only thru this adapter