Acting as EngineerC3Accept
Requirement compliance matrix
Every requirement against what the engineering actually proposes, and the evidence that closes the gap between the two. Nothing here is stored: the matrix is recomputed from the record, so it cannot fall out of step with the records it summarises.
Master prompt section 30, compliance AI
Requirements
0
0 not applicable.
Proven compliant
0
Canonical value, recorded solution and a passing deterministic check.
Not proven
0
Anything that is not COMPLY. Not the same as failing.
Not compliant
0
The proposed solution contradicts the canonical value with no approved deviation.
A requirement reaches COMPLY only when three things exist together: a canonical value, a proposed solution recorded in the configuration snapshot, and a deterministic checker that has passed on that item. A value that matches but has never been checked stops at PARTIAL COMPLY. The default is not compliance, because a matrix that assumes compliance until contradicted is a matrix that reports the absence of checking as success.
Status distribution
Filter the register below.
Compliance register
Select a row to see the evidence chain behind its status.
No requirement carries this status.