create-control-manifest

To generate a programmer-ready rules manifest, extract required, forbidden, and performance rules from Accepted ADRs and engine reference documents. The process writes a flat checklist organized by Foundation, Core, Feature, and Presentation architectural layers to docs/architecture/control-manifest.md.

A control manifest in architecture governance is a flat, actionable checklist that extracts required patterns, forbidden approaches, and performance guardrails from Accepted ADRs. It ensures traceability by sourcing every rule to an architecture document, organized by Foundation, Core, Feature, and Presentation layers.

Extracting architecture rules for Godot engine API constraints involves collecting technical preferences and engine reference documents via globs. The workflow reads these inputs to produce a layer-based rule sheet that captures engine API constraints alongside required patterns and forbidden approaches.

Yes, you can gate the control manifest generation behind a technical director review. The workflow presents a preview summary with rule counts and optionally routes a technical director review gate before writing the final docs/architecture/control-manifest.md file.

You need to regenerate an architecture control manifest when Accepted ADRs or technical preferences change. The regeneration workflow re-extracts rules from all current architecture documents to ensure the programmer-ready checklist maintains complete traceability and reflects the latest governance decisions.

Yes, the control manifest workflow supports performance guardrails and forbidden approaches. It extracts required patterns, forbidden approaches, performance guardrails, and engine API constraints from Accepted ADRs, organizing them into a flat checklist for programmer consumption.