create-control-manifest

You can extract actionable rules from accepted ADRs by filtering architecture decision records for Accepted status and converting implementation guidelines, rejected alternatives, and performance implications into a flat checklist of required and forbidden guidance.

A control manifest in architecture governance is a programmer quick reference document that organizes required, forbidden, and performance rules by architectural layer, incorporating global constraints like naming budgets and deprecated engine APIs.

To generate a developer documentation checklist, read technical-preferences and engine version documents for deprecated APIs and current best practices, then summarize the extracted constraints into a preview before writing the final manifest.

Yes, you can organize extracted architecture rules by Foundation, Core, Feature, and Presentation layers so programmers can easily follow the constraints relevant to their specific work within the application structure.

You need to create a control manifest after your architecture review passes and ADRs are marked as Accepted, requiring technical-director approval at the quality gate before writing the output to docs/architecture/control-manifest.md.

You should include forbidden engine APIs, rejected architectural alternatives, and performance budgets in a programmer rules sheet to ensure developers avoid deprecated patterns and respect global naming and performance constraints.