Add scene imagery requirements

This commit is contained in:
Meta Vens 2026-05-02 17:56:06 +01:00
commit 7fd4a5cba4
4 changed files with 37 additions and 1 deletions

View file

@ -35,6 +35,7 @@ sandboxed training-data pipeline for branching scenes and state consequences.
- Completed story-run setup beats: Maer accepted Sella's bounded diagnostic-contact conditions, extended live ledger exposure, opened the preservation-only diagnostic acoustic channel, and Sella marked decon route Three so the bounded diagnostic sleeve cycles live.
- Next story-run beat: design and generate an interactive-fiction-shaped Cold Wake arc with an opening, branch points, cross-scene consequences, climax, and resolution. Coordinator glue prose is training signal for the future coordinator/story-runtime model.
- Interactive-fiction correction: a full-story pass is not just a linear chain of responder receipts. It needs a beginning-to-ending narrative spine, branch points, and cross-scene consequence carryover so decisions visibly matter later. Responder artifacts should be generated at branch/action moments, while coordinator artifacts track branch flags, relationship deltas, resource costs, unresolved hooks, and later scene consequences.
- Website-content correction: each complete scene should include an art-direction block with establishing shot, light/color, bodies/interfaces, material evidence, branch-visible marks, and an image prompt seed. Visual continuity is part of consequence carryover, not decorative garnish applied after the story escapes containment.
- The Cold Wake v0/v1 fragments are diagnostic seam tests around the clinic climax, not a complete story arc. The next accepted story run should restart from the opening tribunal/route pressure, pass through provenance and clinic contact, and carry consequences into a resolution.
- Still emit training artifacts at material turns: projected local context, responder packet, raw output/capture, leakage audit, reviewed mutation receipt, and aftermath state where relevant.