create-control-manifest

To generate a control manifest from ADRs, you automate the extraction of rules from Accepted ADRs, engine references, and preferences, mapping them to Foundation, Core, Feature, and Presentation layers. This produces a flat, actionable rules sheet at docs/architecture/control-manifest.md.

An architecture control manifest is a flat, actionable rules sheet telling programmers what they must do and never do per system layer. You need one after architecture is complete to ensure implementation consistency and compliance during governance cycles.

You extract actionable rules by parsing Accepted ADRs, technical preferences, and engine reference documentation to separate the 'what' from the 'why.' This aggregates required and forbidden practices into a deterministic, per-layer documentation sheet.

Yes, you can automate control manifest regeneration after ADRs are updated. By invoking the generation process, it reassembles the latest per-layer rules and global conventions from newly Accepted ADRs and engine references into the manifest file.

Yes, manifest generation works with engine reference documentation by extracting rules and mapping them across Foundation, Core, Feature, and Presentation architecture layers. This ensures both global conventions and per-layer rules are captured deterministically.

The best way to organize architecture rules for programmers is generating a flat control manifest that maps extracted rules to Foundation, Core, Feature, and Presentation layers. This separates required and forbidden practices from ADR explanations into actionable guidance.