Flagship film narrative: screenplay v2, captions, claim-ledger revalidation

Context

Sub of epic #15252 (L5 of the lane map, issuecomment-5153855472). Operator brief 2026-08-02: flagship video, 90–150s, heavy drag-and-drop — dockzone hover affordances, perspectives, undo/redo, more multi-window items; single-narrator vs dialogue format open. The narrative is the un-delegable lane retained by @neo-fable per the operator + @neo-gpt-emmy's handoff (voice/API execution = Emmy's Codex-only seam).

Duplicate state: no narrative/screenplay ticket exists (swept live tracker + A2A claims 2026-08-01T22:33Z and again at 22:55Z broadcast window — no competing claim).

The Problem

The film's prior narrative substrate predates the interval: the 14-beat map (rev 1), captions.md draft, and claim ledger C-01..C-08 live in the gitignored production record at their Jul-25 state, while the app gained the completed cross-window journey (#16035), showcase choreography, and now two NEW operator-directed content classes (perspectives, undo/redo) that no beat covers. D-011 stands: the narration transcript derives from the captured cut — but the cut derives from the beat structure, which must be re-mapped first. A flagship bar means the show-order, spoken text, and claim boundary must bind: nothing narrated that the spec cannot witness, nothing claimed that #15243→#15245 gates.

The Architectural Reality

• Executable authority: test/playwright/e2e/workstation/WorkstationFiveBeatNL.spec.mjs (five semantic beats; scenes 4/5 currently red under #16309 — L1 gate).
• Single-window choreography vocabulary: apps/workstation/tour/denseWorkstation.mjs (neo.tour.script.v1, data-only).
• Production authority (append-only, host-local): test-results/dock-wow-demo/PROJECT_RECORD.md §2026-08-02 — carries the operator brief, hold budget (B-01..B-14, ≥54s declared), 51 surviving take logs, voice state (marin standing per AV-007, nova fallback), and the quarantined take-17 corpus.
• New-scope dependency: perspectives (L2) + undo/redo (L3) beats enter the screenplay only when their wiring leaves exist (claimant-filed; #13158 overlap gate). The screenplay must degrade gracefully if L2/L3 land late: core spine first, new beats as additive scenes.

The Fix

1. Beat inventory v2: map the operator's four content asks onto exec-ready vs needs-wiring, against the current spec + tour vocabulary.
2. Screenplay v2: show-order for 90–150s with per-beat spoken-text draft, hold budget honored, format-branched (single-narrator spine vs narrator/engine-voice dialogue — decision folds in Emmy's production take, operator has final ears).
3. Captions.md v2 + claim ledger revalidation: every caption/claim re-anchored to a current spec witness or dropped.
4. Deliverable lands as durable artifacts: screenplay + captions in the production record AND mirrored in a ticket comment (Fable-survival posture — the gitignored record is host-local; the comment thread is the cross-seat truth).

Acceptance Criteria

• Beat inventory v2 posted (exec-ready vs needs-wiring per operator ask, with owning lane/ticket refs).
• Screenplay v2 posted: 90–150s show-order, per-beat spoken text, format decision recorded with rationale (operator ears = final gate on voice/format).
• Claim ledger revalidated: every retained claim cites a green spec witness at the head it will be filmed at; #15243→#15245 boundary asserted.
• All three artifacts mirrored durably (ticket comment or committed doc per operator preference), not context-only or host-only.
• Post-#16309 flag: the reintegration + signature beats enter the screenplay only once L1 is green.

Out of Scope

Take execution, capture staging, TTS rendering (Emmy's seam), L2/L3 wiring implementation, the #16309 fix itself.

Related

Epic #15252 (parent) · #16309 (L1 gate) · #15650 (L4) · #13158 (perspectives overlap) · D#16304 (revision-provenance row for agent-os takes)

Origin Session ID: 355d67d5-9abc-4497-a9e8-937265636376 Retrieval Hint: "flagship film narrative screenplay v2 claim ledger" · production record §2026-08-02