Skip to content
Programming Bible

Cinematic Benchmark — product lock

Status: Locked · 2026-11-02 (standalone host clarified)
Scope: Year-1 standalone UE product — entitled cinematic combat showcase + Benchmark score submit.
Out of scope (now): Lyra / Demo / Full GFP spine · Ladder Demo exit · Full campaign · public free demo · WP page chrome

Authority: GDD cinematic-benchmark · bible docs/28-cinematic-benchmark.md · Motion Matching 2026-11-02-motion-matching-full-design.md · Website Spec ch.10 · Marketing Benchmark teaser (cite only)

1. Decisions locked

Section titled “1. Decisions locked”
Topic Lock
Product name Cinematic Benchmark
Host (now) Standalone UE5 project — not Lyra Experience on the Demo/Full host
What it is Entitled client — cinematic presentation + Motion Matching loco that writes benchmark_runs (API / PUID). Not a Melee Drive combat product now.
What it is not Public free demo · Ladder exit · Website Benchmark page · current Full Plugify work
Motion Matching Shall ship Pose Search loco for CB exit
Ladder Demo Still montage + Motion Warp; MM cut there; CB ≠ Ladder
Full game Integrate later — parked; not a CB exit gate
Look-vs-body MM mesh never owns Look / control rotation
Entitlement Scores only under entitled session / signed client token
Kanban Board cinematic-benchmark — CB cards only (seed prunes Lyra-era cards)

2. Why a fourth product

Section titled “2. Why a fourth product”
Product Job
Full game Ship Year-1 game (later absorbs CB patterns)
Demo (Ladder) Multiplayer Ladder vertical slice
Website WP shell + Benchmark display
Cinematic Benchmark Standalone entitled client (MM + score feed)

3. Exit gate (product done)

Section titled “3. Exit gate (product done)”
Prove Notes
Standalone project boots showcase map Own .uproject
Pose Search loco green Start/stop/pivot; look-vs-body
Cinematic presentation path Authored cine / showcase map
Benchmark submit Entitled → API benchmark_runs

Does not require: Lyra Experience · TFACore/TFACombat · Ladder matchmaking · Full trees/monetary · Full integration.

4. Later — Full game integration

Section titled “4. Later — Full game integration”

When CB has shipped as standalone, plan a separate Full-game integration pass (Plugify / Lyra host as then locked). Until then, kanban card cb-full-integration-later stays parked.

5. Implementer

Section titled “5. Implementer”