Document illustrated IF scene-set pipeline

This commit is contained in:
Meta Vens 2026-05-04 12:23:41 +01:00
commit 0f50cce12d
13 changed files with 260 additions and 61 deletions

View file

@ -32,6 +32,8 @@ backlog, and state ledgers do not slowly melt into one cursed binder.
judgments into training artifacts.
- `docs/architecture/ink-branching-scenes.md`: branch-and-fold, branch
compiler, visual prompt, and IF reviewer contract.
- `docs/architecture/illustrated-if-visual-pipeline.md`: visual replay
contract, geometry authority, scene-set/blockout role, and imagegen boundary.
- `docs/architecture/lore-grounding-digest-format.md`: source-grounding digest
format.
- `docs/architecture/aetheria-lore-grounding-architecture.md`: Aetheria

View file

@ -61,6 +61,8 @@ path is a source-grounded branching-scene data loop:
- Narrative quality reviewer prompt: `prompts/narrative-quality-reviewer.md`
- Visual scene continuity reviewer prompt:
`prompts/visual-scene-continuity-reviewer.md`
- Illustrated IF visual pipeline:
`docs/architecture/illustrated-if-visual-pipeline.md`
- Research-enabled Sella packet: `examples/responder-packets/scene-02-sanctuary-intake.sella_ren.packet.research.v0.json`
- Research-enabled Sella capture: `experiments/responder-packets/cold-wake-sanctuary-intake-sella-research-enabled-v0.capture.json`
- Research-enabled Sella mutation: `experiments/responder-packets/cold-wake-sanctuary-intake-sella-research-enabled-v0.mutation.json`
@ -122,6 +124,12 @@ current gold-data route.
and material constraints.
- If a blocking lore gap appears, patch AetheriaLore narrowly before treating the
detail as available to Ghostlight.
- Generated environment images are mood and material references, not spatial
authority. For multi-angle or branch-consistent illustrated IF, use a durable
scene-set source such as a hand-built 3D blockout, procedural scene file,
layout asset, or camera map with named cameras, staging slots, routes, and
occluders. Imagegen should paint over camera-specific visual input instead
of preserving room topology from prior generated art.
- Technology exploration should emit database-shaped item/assembly/component/
supply-chain candidates mapped toward Aetheria-Economy's CultCache item model.
`CompoundCommodityData` includes colony-consumed manufactured trade goods, not
@ -169,6 +177,12 @@ asteroid aggregate, TCS substrate, seals, supports, and service systems,
with image prompts written as affirmative visible targets. Treat it as
coordinator/IF scaffold training data, not raw responder gold.
Latest visual pipeline lesson: the Pallas Kappa environment overview concept
image is useful as a vibe/material reference, but a follow-up scene prompt did
not preserve the room layout. Do not ask imagegen to act as a CAD intern. For
durable illustrated replay, build or reference a camera-specific blockout and
let imagegen handle the painterly pass.
Kappa geometry correction to preserve across compaction: Service Ring Kappa names this specific standardized industrial spoke manifold service ring: a bounded local access loop around a dense seal-air-thermal equipment cluster. The
loop-inner side exposes manifold faces on the machinery cluster. The loop-outer
side holds worker staging, the baseline anchor rail, lockers, carts, break

View file

@ -67,6 +67,13 @@ Names are handles, not faces. The visual reviewer judges the playable Ink
experience and visual plan; clean-run prose receipts are debugging mirrors, not
the reviewed visual surface.
Generated images are not geometry authority. They can establish visual mood,
materials, and concept direction, but multi-angle illustrated IF needs a durable
`scene_set` source such as a hand-built 3D blockout, procedural scene file, or
layout asset with named cameras and staging slots. For those scenes, imagegen is
the painter/render pass over a camera-specific blockout, not the architect of
the room.
## Important Contracts
- Agent state: `schemas/agent-state.schema.json`
@ -77,6 +84,8 @@ the reviewed visual surface.
- Responder packets: `schemas/responder-packet.schema.json`
- Responder outputs: `schemas/responder-output.schema.json`
- Ink branch contract: `docs/architecture/ink-branching-scenes.md`
- Illustrated IF visual pipeline:
`docs/architecture/illustrated-if-visual-pipeline.md`
- Training stages and corpus gates: `docs/architecture/training-plan.md`
## Current Live Example

View file

@ -70,6 +70,14 @@ not carry live next-action lists.
scene anchors, lore-password image prompts, missing character visibility,
weak stance control, and missing branch/state visual modifiers. It judges
the playable IF plus `.visual.json` plan, not clean-run prose receipts.
- Geometry correction: generated concept art can guide mood, materials, and
environment language, but it is not a durable layout contract. Fixtures
that need the same environment across several beats, branches, or camera
angles should use a `scene_set` source such as a hand-built 3D blockout,
procedural scene file, or explicit layout asset with named camera angles,
staging slots, routes, occluders, and branch-visible state anchors.
Imagegen should paint over a camera-specific blockout, not invent the
room shape from text or a prior generated image.
- The older Cold Wake v0/v1 fragments remain diagnostic seam tests around the clinic climax, not the accepted clean fixture.
- 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.