compliance-trestle
compliance-trestle copied to clipboard
Revise trestle project structure & documentation to clarify public vs private signatures.
Issue description / feature objectives
Currently trestle has most methods scoped publicly. This creates uncertainty around which methods are acceptable to change w/o breaking backwards compatibility.
Identify all critical public api signatures
- OscalBaseModel
- load distributed
- repository api
- CLI signatures
- certain drawio and markdown apis and IO
- load_distributed
- trestle.oscal.*
Document these then:
- Refactor exisiting code to 'hide' imports as appropriate from public consumptions.