create-control-manifest

The control manifest translates accepted ADRs into a single actionable rules sheet for developers, answering what to do and what to avoid. It extracts required patterns, forbidden approaches, performance guardrails, and engine API constraints into a flat document.

The control manifest classifies extracted rules by architectural layer including Foundation, Core, Feature, and Presentation, while applying global rules across all layers. This provides developers with a structured view of engineering guidelines.

You should regenerate the architecture control manifest when ADRs are updated and accepted. Running the extraction process after architecture reviews pass ensures the developer rules sheet reflects the latest technical preferences and engine constraints.

The best way to extract required patterns and forbidden approaches from ADRs is to use an automated control manifest generator. It parses accepted architecture decisions to compile must, should, and always rules alongside performance guardrails into a single document.

Yes, the control manifest output includes engine API constraints and global layer classifications. It extracts these elements from accepted ADRs and engine references, organizing them across Foundation, Core, Feature, and Presentation architectural layers.

No, you should not use this ADR extraction process without passing an architecture review. The control manifest generation applies specifically after architecture reviews pass and ADRs are marked as Accepted to ensure valid engineering rules.