Consider document the current technical state of the Lib 💭

[oseasandrepro]

The idea is to have a technical document with information such as:
Specific LIB flow, and technical attributes since, in this point, it is not strictly adherent to RFC 1057 (Sun RPC);
Communication protocol; packet size exchanged between client and server;
When Binder is active and inactive; When Client Binder call the Server Binder?
When to use threads (what are the general implications of using them here);

the use of code snippets is essential.
The question is: what is the current state of the techniques used under the hood?
And what are the practical implications of use of these techniques

[oseasandrepro]

I think is something that must be done before define the "next step in the project"(Scope Clarification)

[oseasandrepro]

Doc name "Technical Notes".
And this document should use the terminology used in Remote Procedure Call Protocol Specification

References:
What is technical documentation in software development?
A guide to technical report writing - Institution of Engineering and Technology
Writing a technical note
Notes on Technical Writing, A few suggestions on what to do and not to do

[oseasandrepro]

Or "Technical design document (TDD)"