# YSD-0127 — First owned game integration

- **Status:** approved (2026-07-18)
- **Priority:** P0 EXT — blocking (production rollout gated via YSD-0139)
- **Decision owner:** @GreyChimp
- **Drafted:** 2026-07-18 by Claude Code (claude-fable-5)
- **Approval:** approved as recommended by @GreyChimp on 2026-07-18; outcome
  recorded in decision-log.json; review by 2027-07-18

## Question

Which owned title/build gets instrumented (Tier B/C) study first?

## Recommendation

V2 (the proposal's recommended candidate): its replay
(libs/aphrodite/game-runtime OSHRPLY format) and player-behavior-heatmap
primitives (apps/v2/player-behavior-heatmaps) already exist, along with
telemetry schema-migration, session-reconstruction, and privacy-compliance apps
— the smallest instrumentation gap of any owned title.

## Options considered

- V3–V10 titles — deferred: fewer existing telemetry primitives.
- External commercial titles — excluded by design (missing-by-design row in the
  reuse ledger; video-only Tier A only).

## Consequences

- Section 12 Tier B/C items target V2 first; the cross-game study contract
  (YSD-0158) is designed against V2 but must not hard-code it.
- Replay/telemetry access goes through the Bellona/product-runtime adapter,
  never direct imports.

## Machine-enforced outcome (once approved)

Game-connector feature flags enable only V2; anti-feature tests (Section 21)
prove external titles cannot reach instrumented paths.