QA TEMPLATE / SAMPLE
08 Dashboard Status Contract
Public projection | Sources, status and publication boundaries
Synthetic Order Book teaching scenario, not a real exchange test. Based on this site's stale-sequence Fail Demo. Prices, quantities and times are supplemental teaching assumptions. Runs, defects and evidence names are synthetic; there was no real product execution, attached evidence or customer approval.
What this document answers
08 Dashboard Status Contract defines how an approved 07 Release Quality Summary becomes a public projection. Runs retain execution facts, 07 retains judgment, and 08 defines publishable fields and validation.
Blank template
[Required] applies to every case. [Conditional] is required when applicable; explain when it is not. Copy the text into your case documents and replace the brackets. This static page has no editing or saving function.
[Required] Assessment source / version, contractVersion, schema, exporter / policy / publisher workflow versions and SHAs: [ ] [Required] Public subject: repository / release / branch / fullSha; objective, environment, testedScope, excludedScope: [ ] [Required] Approved releaseAssessment: status / rationale / decidedAt / expiresAt / qaOwner / reviewer / decisionOwner: [ ] [Required] summary: effortLevel / coverage / quality / comment: [ ] [Required] productAreas: id / name / effortLevel / executionState / coverage / targetCoverage / quality / comment / evidenceLinks: [ ] [Required] gates: id / title / note / state; runs: runId / executedAt / evidenceUrl: [ ] [Required] provenance: generatedAt / syncedAt / sourceSha; dataStatus / publicDisclosure: [ ] [Required] Checks: matching subject, authorized source, schema / version, freshness, blocker / waiver, allowlist / links, secrets / PII, atomic manifest / last-known-good: [ ] [Required] Disclosure reviewer / outcome / time, allowed and prohibited fields: [ ] [Required] Publication and correction: generation / sync times, manifest / hash, last-known-good, correction / withdrawal procedure, rollback owner, post-publication smoke evidence: [ ] Generate a read-only projection from approved 07. Do not enter a second decision or produce a publishable snapshot without approval.
Filled example: planning a Blocked projection
| Field | Synthetic example |
|---|---|
| Source / version | DEMO-QUALITY-MDQ v1.2; contractVersion 1.0.0; schema/test-status.schema.json; current policy 2.1.0. Exporter / publisher SHAs are pending; no approved source exists. |
| Subject / scope | DEMO-BOOK / build-demo-1; real repository / branch / fullSha Unknown. Reference 07 for the three cases and exclusions. Do not invent a full SHA or produce publishable JSON. |
| Product status / rationale | Teaching derivation: Blocked. DEF-MDQ-004 is an unresolved S1 and TC-MDQ-017 has a synthetic Fail. QA / reviewer / decision owner and decidedAt / expiresAt have no approval. This is not a formal release assessment. |
| Data status | No formal snapshot is configured: display label Not Configured. There is no real sync or freshness evidence; a teaching date cannot establish Fresh. |
| Summary / Product Area | Teaching area Order Book: quality=bad, executionState=complete (all three synthetic cases completed). Coverage / effort are unapproved and cannot be inferred from 100% completion. The comment cites the synthetic S1; formal evidenceLinks require approval. |
| Gates / Runs / provenance | G3 / G6 have no formal evidence or approval. The teaching Run references DEMO-RUN-FAIL-001 and must not be represented as real execution. generatedAt / syncedAt / sourceSha have not been produced. |
| Disclosure checks / publication | Only synthetic IDs, teaching assumptions and roles are included. Real schema / subject / freshness / authority validation has not run. publicDisclosure, disclosure reviewer / time, manifest / hash, last-known-good, rollback owner and smoke evidence require real engagement inputs. This page publishes nothing. |
Separate product status from data status
| Status | Meaning |
|---|---|
| Blocked | A trustworthy, same-version unresolved S1, unaccepted S2 or critical-path nonconformance. Retain known issues when evidence expires and list missing data separately. |
| At Risk | No blocking issue, but remaining defects or accepted risk exist. Record accountability and follow-up; this does not authorize release. |
| Unknown | No trustworthy known blocking or residual issue, but criteria, evidence or review are incomplete. Corrupt or subject-mismatched data cannot establish product facts. |
| Ready | All four dimensions support test delivery, no known residual defect / accepted risk remains, and a human-owned assessment exists. Publication still needs Go. Historical Ready is not current approval. |
| Data Status | Fresh / Stale / Invalid / Not Configured / Unreachable describe source availability. They do not directly establish product quality or provide live monitoring. |
Correction and recovery
On source revision, identify affected cases and append required Runs and reviews. Invalid data keeps the last-known-good snapshot plus a failure marker; do not rewrite old snapshots. Corrections, withdrawals, rollback and post-publication checks follow existing ownership. Sending, publishing or deploying still requires authority. See source revisions, review disagreements and AI misjudgments.