What problem does it solve? It prevents two costly Rust build failures: message types discovered crate-by-crate that desync and cause tokio channel panics, and architectural mistakes that get replicated correctly-but-wrongly across every crate. It freezes all contracts and validates the architecture before any code is written. ## Core Features & Use Cases - Crate decomposition: Splits the requirements record into crates where each crate is exactly one sealed responsibility, including explicit protocol and store crates. - Frozen message contracts: Defines every claw-protocol message type in full before any crate is built, with a versioned amendment protocol for later changes. - DAG and build ordering: Produces the dependency DAG, a topologically sorted build order, and the bus coupling order for step 4. - Independent review gate: Requires a second model to review crate boundaries, contracts, and the DAG against Ordo doctrine before the gate passes. - Use Case: After the requirements record exists for an Ordo app, run this step to produce the versioned blueprint that the crate-build step consumes. ## Quick Start Run the ordo-build-blueprint step on my requirements record to produce the frozen message contracts, dependency DAG, and topo-sorted build order before any crate is built.
