Eve library

V4 Match Rail channel boundary

Other

Revision 1

On this page

@oshun/v10-rail-channel-v4-match is the fail-closed activation seam for the future V4 Match channel. It is intentionally not a production registration and does not claim that V4, its match feed, or its shared live-media tenant has launched.

The boundary composes three existing owners rather than copying them:

  • @calliope/match-commentary remains authoritative for grounded bias review and commentary quality clearance;
  • @uzume/broadcast remains authoritative for RC.1 ambient/highlight director profiles and R0.3 daypart switching;
  • the future RB.3 v4-match tenant remains authoritative for a live, ready playback projection.

Activation requires all of the following in one call:

  1. trusted V4 launch evidence with build, platform-certification, live-ops, online-service, commentary, and tenant receipts;
  2. an exact v4-match live/ready program using HTTPS HLS or DASH;
  3. a current opt-out decision covering the exact match participant set;
  4. owner and every contributing-friend receipt when personal voice cloning is requested; and
  5. a matching Calliope package whose bias and quality statuses both clear.
  6. a configured Rail FirstPartyLiveVideoGate backed by the shared RB.3 playback authority.

Missing configuration, unavailable authorities, stale/partial consent, participant opt-out, gate exceptions, contradictory gate results, cross-tenant media, scheduled launch state, and non-live publications all hold or reject activation. Only a successful activation creates a ring-valid spectator manifest. There is no player face yet because V4 has no authoritative campaign simulation that advances the user's squad between sessions.

Run the focused gates with:

sh
pnpm nx test @oshun/v10-rail-channel-v4-match
pnpm nx typecheck @oshun/v10-rail-channel-v4-match
pnpm nx lint @oshun/v10-rail-channel-v4-match