create-control-manifest

A Control Manifest solves scattered architecture decisions by consolidating accepted ADRs, technical preferences, and engine constraints into a single actionable document with clear required and forbidden rules classified by system layer.

You extract architecture rules and performance budgets by loading accepted ADRs and technical preference documents, filtering out non-accepted records, and categorizing the extracted constraints into Foundation, Core, Feature, and Presentation layers.

Yes, you can enforce deprecated engine API restrictions in game development workflows by incorporating engine reference documents into the Control Manifest generation to explicitly list forbidden APIs and engine compatibility guardrails.

Generate a control manifest after architecture review by loading accepted ADRs, previewing the extracted required and forbidden rules, optionally gating via technical-director review, and writing the finalized layer-based rules to docs/architecture/control-manifest.md.

Yes, the control manifest skips non-accepted ADRs during rules extraction to ensure programmers only receive implementation guidance and traceability from formally approved architectural decisions.