create-control-manifest

To generate a control manifest from ADRs, run the create-control-manifest workflow after architecture review. It parses Accepted ADRs, technical preferences, and engine references, then outputs a flat rules sheet at design/architecture/control-manifest.md.

A control manifest is a flat, actionable rules sheet used to guide developers across system layers after architecture review. It consolidates ADRs and engine docs to specify what to do and what not to do, reducing ambiguity and speeding implementation.

You can organize engineering guidelines by architectural layer by generating a control manifest. It automatically duplicates and categorizes rules into Foundation, Core, Feature, and Presentation layers, reusing rules when ADRs span multiple layers.

Yes, you can regenerate the control manifest after ADRs change. Running the create-control-manifest workflow again updates the rules sheet to keep your developer guidelines synchronized with the latest technical preferences and engine references.

Before generating an actionable program rules sheet, you need completed and Accepted ADRs, technical preferences, and engine reference docs. The workflow parses these inputs after your architecture review passes to produce the manifest.

Yes, the control manifest output includes the primary rules sheet at design/architecture/control-manifest.md, along with optional resources. If present, it also outputs supporting files in the scripts/, references/, or assets/ directories.