create-control-manifest

Extracting architecture rules from accepted ADRs involves generating a centralized Control Manifest that consolidates required and forbidden patterns, performance guardrails, and engine API constraints into an actionable per-layer rules sheet.

An architecture control manifest provides programmers a per-layer rules sheet defining required and forbidden patterns, derived from accepted ADRs, technical preferences, and engine reference docs.

Consolidate tech preferences and engine references by running a manifest update command that classifies rules across Foundation, Core, Feature, and Presentation layers, outputting a ready-to-review file at docs/architecture/control-manifest.md.

Regenerate an architecture manifest whenever new ADRs are accepted, ensuring the control rules sheet captures the latest required and forbidden patterns, performance guardrails, and engine API constraints.

Yes, the control manifest classifies extracted rules by architectural layer, organizing global conventions and specific patterns across Foundation, Core, Feature, and Presentation layers.

The best way to enforce engineering governance from ADRs is to transform them into an actionable architecture manifest that explicitly dictates required and forbidden patterns, shifting from explaining why to specifying what to do.