G33 — Requirement, test, evidence, and acceptance graph · Graph systems

183 words. Researched design, reviewed 2026-09-12: a library view or proposed design with its sources stated; not a deployed system, a live audit or a provider requirement. Source: Graph/G33-requirement-test-evidence-and-acceptance-graph.md. Graph systems, shelf 5 of 8; library release 2026.09.12-g40.

Status: NEW RESEARCHED DESIGN; not deployed
Reviewed: 2026-09-12
Nature: private library operating design
Priority: P0
Accountability: R21, R26, R25, R14

Question

Which executed check supports each release or publication requirement?

Nodes

Requirement; Test definition; Test run; Build; Evidence; Verdict

Relationship sketch

test → requirement
run → exact build
verdict → observed evidence

Evidence inputs

Predeclared contract, real runs, actual artifacts, timestamps, reviewer identity and independence declaration.

Implementation

Connect outcomes to exact tested builds. Keep self-review distinct from independent execution. A structural check catches missing records but cannot prove truth or authorize deployment.

Acceptance checks

Every required pass has an executed matching test
Missing evidence remains blocked
A fixture pass is never reported as a client-site pass

Do not infer

A green JSON validation result does not prove a live website or mailbox works.

Publication boundary

Private evidence; only approved bounded public claims.

Source basis

S16, S14. See Research/sources.json. Sources support the primitives or named technology. The organization, labels, actions, and acceptance contracts in this catalog are this library's design, not claimed provider requirements.