Quality Contract and Certificate Technical Specification
“Produce a quality proof package” is architecture doctrine, not yet an implementable contract. A real system needs stable subjects, schemas, lifecycle states, evidence sufficiency rules, deterministic decisions, signatures, invalidation, re
A focused view of boundaries, contracts, state, authority, failure paths, and tradeoffs drawn from this chapter.
Reconstruct and defend this chapter’s architecture.
Reconstruct the architecture, name each boundary, and defend the tradeoffs.
Open the source exercise
Draw the four records and their state machines. Issue a certificate, then change the Plan, discover a compromised validator, and observe a production regression. Explain invalidation, suspension, revocation, supersession, affected evidence, and consumer checks for each event.
4. Tradeoffs
A certificate creates a strong integration boundary but can encourage binary thinking. Preserve the underlying findings, uncertainty, waived claims, and scope. Short validity improves safety but increases re-evaluation load. A centralized issuer simplifies control but is a high-value trust root; independent verification and key protection are mandatory.
5. Current Mission Control Implementation
Mission Control already has ingredients: approved Plan revisions, WorkOrder acceptance criteria, verification receipts with validity, approval decisions, QC runs/evidence packs, GitHub check ingestion, deployment/release-gate records, run artifacts, and audit events. A staged, uncommitted continuous-quality plan proposes evidence envelopes, quality findings, gate decisions, reconciliation, and the principle that the approved Plan is the top-level contract. Its SHA-256 is 31e3f6fc44824b643ef5bfa3389ba3da1e0e6b1f6827f66fdb63efcbb4c9313b.
Those proposed tables and APIs are not yet demonstrated product capability. Current qcRuns.execute uses mock adapters and the release gate is shadow-only. Mission Control should call the V1 user-facing artifact a Quality Proof Package until signing, verification, status, and revocation are implemented. “Quality Certificate” should be reserved for the portable technical contract defined here.
Review this chapter.
Challenge a claim, boundary, missing failure mode, unclear term, or unsupported evidence statement.
- Claim
- Boundary
- Failure
- Evidence