documentation-automation

Process documentation automation generates EDPS-compliant documents across hierarchy levels. It creates main.md, process.md, collaboration.md, and domain-model.md from input files like collaboration.md, hierarchy-metadata.json, and domain-concepts.json.

Activity diagrams and sequence diagrams are generated automatically within process.md and collaboration.md respectively. The automation creates level-specific activity diagrams for process descriptions and EDPS-compliant sequence diagrams for collaboration flows.

To generate domain-model.md with scoped entities, you need collaboration.md, hierarchy-metadata.json, and optionally domain-concepts.json from your process folder. The automation produces domain-model.md with entities scoped to the boundary's participants.

You should regenerate process docs from collaboration.md when existing documentation needs updating. Running the automation rebuilds all level documents including main.md, process.md, collaboration.md, and domain-model.md to ensure consistency across the hierarchy.

Documentation automation can run independently by regenerating from collaboration.md. However, its primary trigger applies after creating a new process folder via hierarchy-management, utilizing hierarchy-metadata.json for navigation and breadcrumb generation.