Objectives
Document the steps that a project performs in order to provide some service or functionality. This could include what actions each Actor performs and how they interact with each other.
Resources
Architecture diagrams for each Actor can be found in the presentation to provide visual representation of how sub-project interact. These are also available in project repos.
It may be useful to create a subsection for each set of projects to drill down on interactions between individual components.
Example text
## compliance-trestle
Agile Authoring workflows triggered by pushes to the dev branch run `compliance-trestle` and determine
the state of the local git repository and if there is a diff that need to be committed and
pushed to remote that can be used by C2P to transform to policy artifacts.
## compliance-to-policy
C2P reads the OSCAL document in JSON with validation information to determine what plugins are selected.
Once plugins are selected by ID, C2P discovers plugin metadata through the plugin manifest in JSON.
C2P calls each subprocess by name based on the plugin manifest data.
After launch the plugin runtime behavior is customized through configuration options and defaults
provide by the manifest and user selections provided to the plugin by calling the `Configure` method.
See #104
Objectives
Document the steps that a project performs in order to provide some service or functionality. This could include what actions each Actor performs and how they interact with each other.
Resources
Architecture diagrams for each Actor can be found in the presentation to provide visual representation of how sub-project interact. These are also available in project repos.
It may be useful to create a subsection for each set of projects to drill down on interactions between individual components.
Example text
See #104