arch

Contract-driven architecture prevents late-stage changes by decomposing a project into subsystems with explicit constraints and boundaries, producing a living spec that tracks state as the project evolves.

The best way to plan build order is by defining subsystems with explicit contracts and constraints, which coordinates team work through a manifest-driven build workflow and phase tracking.

To generate an initial architecture spec for a greenfield initiative, provide a project brief or SEC-ticket path to establish a concrete architectural plan with subsystem boundaries.

This architecture blueprint works for both greenfield initiatives and after an /arm brief, establishing a concrete architectural plan with contract boundaries, build order, and phase-tracking.

You need to define architecture at the contract boundary when global architecture suffers from ambiguity, requiring subsystem decomposition with explicit contracts and constraints to enforce clear boundaries.