Date: 2026-07-27
Status: strict flagship contract implemented; execution remains blocked.
scripts/v5/verify-flagship-evidence.mjs requires the complete V5-001
authored-world package from the same source commit and completion time, then
adds six flagship checks:
- distinct side-quest/daily-detective and replay-highlight outputs, each with immutable source and cooked artifacts, cooked-build placement, runtime load, runtime completion, and receipts;
- the exact successful
RunUAT BuildCookRun/Linux/ueagentidentity bound to a nonempty hashed cooked archive; - named human approval, rights and consent receipts, signed provenance, signature and trust-list verification, and an immutable signed bundle;
- a blinded, production-representative comparison against the best authored baseline with at least 30 participants, a passed quality gate, majority preference, and a signed report; and
- actual control-plane canary start, telemetry-driven defect discovery, verified revision, rollback to the previous revision, and recovery receipts.
The retained input and reproducible report are
evidence/v1-v9/V5-003-flagship-evidence.json and
evidence/v1-v9/V5-003-flagship-readiness.json. Both honestly represent a
not-yet-run flagship and all six checks are blocked.
Verification:
node --test scripts/v5/verify-flagship-evidence.test.mjsnode --check scripts/v5/verify-flagship-evidence.mjs- strict CLI exits nonzero on the retained empty package
--reportreproduces the retained readiness JSON
No V5-003 checkbox is closed. The contract does not substitute for the missing playable content, cook, human study, provenance, or operations execution.