Skip to content

Afterglow Story-to-Screen CI/UAT: verify Post-it → Writing → Outline → Storyboard → Previs → Scene Workspace → Production #2174

Description

@BryanHarrisScripts

Parent

#2165 Writer-to-Screen Convergence

Objective

Turn the completed writer-to-screen architecture into a deterministic acceptance path using Afterglow as the canonical worked story.

Deterministic CI lane

For selected Afterglow fixture Blocks/Mini-Blocks, CI verifies without cloud spend:

  • Story Card identity/order/lock state;
  • written Block title/subtitle/source refs;
  • Outline structural fidelity;
  • Storyboard provenance and accepted/candidate/missing visual states;
  • Previs dependency and timing/motion evidence where present;
  • Scene Workspace Dialogue/Action/Shot/Audio identity/order/timing contracts;
  • provider-neutral Production compilation;
  • revision/staleness behavior from Creative revision propagation: upstream Block changes invalidate only dependent downstream work #2172;
  • no manufactured completion.

The test checks continuity/provenance/completeness, never subjective artistic quality.

Human/WebMCP UAT lane

A Human can load Afterglow and navigate the same story at any stage:

STORY CARDS → WRITE → OUTLINE → STORYBOARD → PREVIS → SCENE WORKSPACE → PRODUCTION

At every stage the same project, Act/Sequence/Block/Mini-Block and title/subtitle remain visible and navigable.

Scope progression

Start with one reviewed Block as the executable end-to-end slice. Expand to coverage of all 24 Blocks / 96 Mini-Blocks as upstream mappings become reliable. Do not fake downstream artifacts to claim full coverage.

Exit criteria

  1. One Afterglow Block passes the full deterministic chain end-to-end.
  2. Full 24/96 structural/source fixture coverage is reportable.
  3. Human/WebMCP can jump between stages without losing story identity.
  4. CI remains Local/offline by default.
  5. Provider-backed generation is separated into explicitly authorized UAT/Responsibility Runs.
  6. Missing evidence is a truthful state, not a test failure patched with filler.
  7. Regression evidence identifies the exact story address/stage that broke.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions