Production Packet Compiler
A deterministic browser-local research instrument.
f4e50e8b- IDEA
- PACKET_DRAFT
- PLAN_READY
- APPROVED
- RENDERING_SIMULATED
- RETURNED
- REPAIR_REQUIRED
- ACCEPTED
Each control executes a declared browser-local transition. Repeated dual-outcome controls alternate deterministically.
NOT YET EXERCISEDReference roles and order are explicit.
NOT YET EXERCISEDChanging configuration does not execute or spend.
NOT YET EXERCISEDRender path remains blocked before approval.
NOT YET EXERCISEDRepair packet names exact violations and preserves accepted references.
No transition yet. Operate a declared control.
This transparent browser-local instrument teaches the authored state contract. Exercising an assertion demonstrates fixture behavior only; it is not evidence of production performance, compression ratio, model uplift, cognition, safety, or universal correctness.
Purpose
Compile a creative idea and references into an approved, costed, continuity-aware production packet and Omni sequence sheet.
Mechanism
The compiler assigns reference roles, builds a timeline and shot graph, applies skills, selects a provider lane, estimates cost, and blocks render until plan approval.
Deterministic fixture
A fifteen-second music-video scene with one character identity reference, environment, lighting plate, six beat images, and two provider profiles.
The fixture must live in content/demos/d20-production-packet-compiler/fixture.json, validate before the demo renders, and be resettable without a network call. A future live adapter may be added behind a visibly separate mode.
Required controls
- Add reference
- Assign role
- Reorder Omni panels
- Apply Production Skill
- Edit shot beat
- Change provider
- View estimate
- Approve plan
- Simulate first render
- Generate repair packet
Visible states
IDEAPACKET_DRAFTPLAN_READYAPPROVEDRENDERING_SIMULATEDRETURNEDREPAIR_REQUIREDACCEPTED
Every state must have text, iconography, and a non-color-only distinction. State transitions are logged in an in-memory demo receipt visible in the inspector.
Core assertions
- Reference roles and order are explicit.
- Changing configuration does not execute or spend.
- Render path remains blocked before approval.
- Repair packet names exact violations and preserves accepted references.
Layout
The page contains:
- a concise mechanism explanation;
- the interactive stage;
- a state and evidence inspector;
- a reset control;
- a “what this proves / what it does not prove” panel;
- links to the related paper and benchmark contract.
On narrow screens the inspector becomes a bottom sheet. The stage must remain usable at 360 CSS pixels.
Accessibility
- All operations are keyboard reachable.
- Pointer gestures have button or keyboard equivalents.
- Animated transitions honor
prefers-reduced-motion. - Focus remains visible and returns predictably after sheets close.
- Diagrams expose concise text alternatives.
- Status is announced through a polite live region only when the user initiates the transition.
Instrumentation
Record locally:
demo_id
fixture_version
action
prior_state
result_state
validation_result
timestamp_relative
Do not send telemetry. Provide “Export demo trace” as JSON for debugging and reproducibility.
Automated tests
- fixture schema validation;
- deterministic reset;
- every required control transition;
- every assertion above;
- invalid and stale fixture handling;
- keyboard path;
- 360 px and 1440 px screenshots;
- zero critical console errors;
- no request to a paid API in default mode.
Publication boundary
Provider renders are simulated unless a separately authorized integration is active.
The interface must never convert illustrative values into a benchmark claim. A measured result appears only when linked to a versioned run receipt.