Date: 2026-07-27
Outcome#
V5 now has a governed Metis authoring/cook boundary at
apps/v5/metis-training-bridge. It uses the shared
@metis/game-bridge-contract to admit exact released publication and lesson
records and emits a deterministic v5.metis-training-range-content-manifest.
The bridge is locked to the authoritative checked-in
V5Mode_Training_Range/Content/Data/training_range_manifest.json. That manifest
defines exactly six verification bays:
- weapon training;
- AI dummies;
- vehicle handling;
- sign/power tuning;
- vision-cone calibration; and
- frame-data display.
The tests parse that JSON and require exact equality with the bridge contract.
Authority boundary#
Each bay must bind one exact released Metis lesson. Shared admission requires a released API-export package, operator approval, cleared rights, verified provenance, approved Sophia-source-of-record grounding, learner disclosure, accessibility and fallback readiness, and safe labeled media.
The resulting content explains V5's authored validation surfaces. It cannot tune damage curves, vehicle handling, sign powers, AI behavior, or frame data. V5 exclusively owns range execution, live metrics, and completion. The no-fail range remains leaderboard-free and the bridge cannot mutate mastery.
Live metric frames, gameplay simulation, rollback simulation, accuracy/time/hit metrics, gameplay telemetry, combat outcomes, trial scores, leaderboard rank, authoritative tuning values, AI Director state, and rollback state are rejected before canonical provider reads.
Automated verification#
Focused verification passed:
- V5 typecheck;
- V5 Vitest — 1 file, 14 tests;
- V5 lint and build;
- canonical Metis contract generation check;
- Nx project discovery and root module-boundary lint; and
- targeted Prettier validation.
Coverage includes exact Unreal-manifest equality, deterministic output, authority flags, every forbidden runtime-input class before I/O, manifest drift, unreleased packages, and cross-bay lesson binding.
Scope boundary#
This closes the actionable V5 canonical-provider admission seam. It does not claim a cooked Unreal consumer, in-engine instructional rendering, or runtime authentication. V6–V8 bridges and game-runtime consumption remain open, so the composite V9-004 checkbox remains open.