sb-validate-design

Run the structural checks first with specbind spec status, check traceability --for-design, and check contracts, then read the requirements, design, and contract artifacts. Judge readiness against the CLI-reported active requirement set and return a READY or NOT_READY verdict with findings.

A READY verdict asserts every active requirement is substantively realized, the owned boundary is explicit, work decomposes into bounded tasks, the document is self-contained, and complexity fits the architecture. Any gap produces a BLOCKING finding naming the endangered requirement and consequence.

No. The validator is strictly read-only: it never edits the design or contract, never invalidates the design gate, and never records machine state. A NOT_READY verdict is information for the user; lifecycle changes belong to the Plan orchestrator.

The validator reads the complete current design independently, then accounts for every prior BLOCKING finding ID exactly once, marking each RESOLVED or still BLOCKING. If the supplied history is incomplete or ambiguous, it returns NOT_READY rather than manufacturing a clean mapping.

Deferred findings are written only to the destination named by the project's deferred adapter, read via specbind adapter read deferred. If the project has no such destination, the validator says so in one line and records nothing rather than inventing a location.