sdd-verify

To verify an implementation matches design specs, you execute a verification workflow against the change artifacts to validate conformance with task requirements and produce a structured compliance report. This process checks completeness, correctness, and design coherence.

Change verification is the process of proving an implemented change adheres to defined specifications and designs by executing the intended workflow. It validates conformance across completed or partially completed changes to generate audit-ready execution evidence.

You generate an audit compliance report by running a verification workflow against target change proposals and design artifacts. This produces actionable evidence covering correctness and design coherence to validate compliance before release or archive.

Yes, verification can be applied to completed or partially completed changes across multiple projects. It handles change proposals, specs, and design artifacts to validate conformance and produce a verifiable compliance report regardless of completion status.

Executing verification requires structured guidance, persistence contracts, a registry of changes, and execution evidence. These inputs validate compliance against provided change artifacts to generate a full compliance report for audit purposes.

You should run design verification before archive or release when a change requires proof that the implementation matches defined specs and tasks. It ensures completeness and correctness through executed verification and actionable evidence generation.