Screenwalk 2026-10-11 — What an Episode Holds: from a proposal to its doors#

A brief for the screenwalk Guillaume records on 2026-10-11 from two sessions: the Claude Code seat miadi-episodic-memory-schema-and-mw-261010 on gaia (Mia, Fable 5.1) and the ChatGPT thread where EchoLune carries the Author's Desk prototype prompt. The walk is held by miadi-chronicle://552 (What an Episode Holds); its takes land in that episode's captures/ through phone-capture, and its review becomes the episode's first reviews: entry.

What the walk shows, in order#

The question. Guillaume's five-part request of 2026-10-10 (prototype, notebooks, Langfuse per domain, tide sessions, RISE specs), decomposed in Episode 076's .pde/.
The page. The proposal "What an Episode Holds" (a Claude artifact): the before/after figure, the room wireframe with the reach switch, the coded cards, the second opinion's corrections C1–C9.
The engine. Every card scored with Jev 1.13.0 through skills/proposal-visualization/scoring/: the three lists (would do now, after your go, needs you), the D1 rule above the number, the go given at 23:11, the two readings to rule against (A1, E7).
The doors. Episode 120's room with its new cards: Prototypes (the published address for a reader, the v0 editing address only for a writer), Traces and prompts (two ceremony traces and the prompt, no provider named in the manifest), Notebooks (typed), Specifications. The chips miadi-notebook:, miadi-prototype:, miadi-tracing: and rise:// opening through /api/chronicle/open.
The prompt in five versions. v1 (EchoLune), v2 (too much), v3 (one short block), v4 and v5 (EchoLune's reconciliations), side by side in Episode 076's inquiry, with the Implementation & Gap Report.
The text. rise://jgwill/llms-txt/llms-rise-framework.txt@27cf18f, RISE 1.3.0: Exportation names where specs land and how the export is recorded in the episode.
The provider. @miadi/tracing over @miadi/tracing-langfuse, reading the Ceremony project through the v4 observations API; the dashboard's deprecation notice and what answered it.
This episode. miadi-chronicle://552: the page's address, the specs, the prompts and the inquiry held as lists, and the steer written for the session that revises app/api/session.

Questions the walk asks Guillaume#

D-a: publish the five packages and rebuild :3335 (A6).
D-b: miadi-tracing: canonical with miadi-trace: and miadi-prompt: as aliases, or the short forms.
D-c: story prompts (miadiStory-*, miadiWrite-*) move to the Story project (O14).
Q2 of the sessions route: Miadi or asterion; the steer in Episode 552 proposes the join as a package and the episode-facing route in Miadi now.
The rulings on A1 and E7 that calibrate the thresholds.

Plot threads to carry (for the fiction and the report)#

What an episode holds: from two typed lists to six, each walking the same four steps.
The engine decides what is obvious: a proposal that says what it will do before it is read; an empty first list as a result.
Two agents, one prompt: a terminal seat and a ChatGPT thread versioning the same Langfuse prompt, with the human choosing the length.
An address is not a location: the resource-addressing foundation applied to notebooks, prototypes, traces and specs.

Beats#

The request arrives with five parts and a feeling that the cycle is not closed.
The survey finds the three Langfuse key sets unused and the notebooks typed nowhere.
The second opinion says the manifest is served to every reader; the editing address leaves it.
The engine scores: nothing crosses 0.8; the go comes anyway.
Three doors open in one evening; Episode 120 holds its prototype and its traces.
The prompt goes to 21k characters and comes back to 13k; EchoLune takes it to v5.
The dashboard flags a deprecated call; the provider is rewritten against observations.
The episode is minted, and the walk is scripted before it is recorded.