Eve library

V4-002 — Flagship commentary evidence boundary

Evidence

Revision 1

On this page

Date: 2026-07-27

Status: strict evidence contract implemented; flagship execution remains blocked.

Result#

scripts/v4/verify-flagship-evidence.mjs now evaluates one coherent V4 flagship package. It first requires the complete V4-001 provider, governance, localization, review, and integrated-runtime contract to be ready from the same source commit and completion time. It then requires:

  • one immutable real-match event log with uniquely identified factual events;
  • distinct live end-of-match and live-spectator Calliope and Psyche requests, receipts, grounded event IDs, immutable scripts/audio, active consent, native-speaker and bias review, watermark, provenance, and observed runtime playback;
  • actual control-plane intervention, canary, rollback, and recovery receipts, with verified previous-revision restoration and recovery within five minutes;
  • a blinded, production-representative comparison against authored commentary with both player and commentator cohorts, at least 30 total participants, at least 10 per cohort, signed reports, and majority preference for the generated candidate in each cohort; and
  • the exact successful V4.IntegratedRuntime invocation plus immutable playback media, Automation log, and Automation report for the same match, commit, and V4 project.

Provider IDs marked fake, fixture, mock, stub, synthetic, or test are rejected. End-of-match and spectator requests and audio must be distinct. A static manifest, skipped run, workflow artifact label, or detached media file cannot pass.

The retained input is evidence/v1-v9/V4-002-flagship-evidence.json; the byte-reproducible evaluation is evidence/v1-v9/V4-002-flagship-readiness.json. It is blocked on all six checks because no coherent real-match, provider/human-review, runtime-media, and operations package exists in the workspace. The successful standalone V4-001 integrated-runtime run has no match playback media and is not substituted for that flagship package.

Verification#

  • node --test scripts/v4/verify-flagship-evidence.test.mjs
  • node --check scripts/v4/verify-flagship-evidence.mjs
  • node scripts/v4/verify-flagship-evidence.mjs --evidence=evidence/v1-v9/V4-002-flagship-evidence.json (expected nonzero while evidence is absent)
  • the same command with --report reproduces the retained readiness JSON

No V4-002 checkbox is closed. This change defines and tests the acceptance boundary; it does not fabricate the external provider, participant, operator, or Unreal executions.