What an Episode Holds

Minted 2026-10-10 late evening by Mia (Claude Code, Fable 5.1, tmux miadi-episodic-memory-schema-and-mw-261010) from one day's work with Guillaume, so that the work itself is an episode: a reader opens each thing it made from this room, and the screenwalk of 2026-10-11 starts here.

Where it stands (2026-10-11, 23:00)#

• The proposal page is a Claude artifact, revision 4: What an Episode Holds. Its HTML, its Jev scores, the request in Guillaume's words, the expectation written before the review and the review itself are in this episode's inquiry/ folder, woven from Episode 076's inquiry (jgwill/miadi-orchestration-kit#80).
• The code is on main of jgwill/Miadi under jgwill/Miadi#769 and published: @miadi/episodic-memory-schema 0.15.0, @miadi/tracing 0.1.0, @miadi/inquiry-weave 0.17.0, @miadi/tracing-langfuse 0.1.0, @miadi/reference-ui 0.2.0 (pnpm, leaf-first). Four typed lists (notebooks:, prototypes:, tracing:, rispecs:), their doors, tools and room cards; the addresses miadi-notebook:, miadi-prototype:, miadi-tracing: (aliases miadi-trace:, miadi-prompt:) and rise:// resolved through /api/chronicle/resolve and opened through /api/chronicle/open; sessions read through the one join, @miadi/hooks-interpreter 0.4.0 (A10). The kit plugin is 0.3.8 (inquiry-weave 0.17.0). :3335 was rebuilt from main (BUILD_ID Sq8w_RsF5eXRqUqMDZCsH) and again for A10.
• Before publishing, an Opus review of the six commits found 27 things; 22 were fixed (jgwill/Miadi 2f713843). The three that mattered most were not in my expectation: ./references had grown a node:fs import so reference-ui no longer bundled for a browser; a versioned prompt address asked the wheel for a node id with the version; the trace name lives in Langfuse's trace_context field group and the fake answered it regardless. The synthesis is inquiry/…/review-synthesis-769.md.
• miadi-chronicle://120 holds its prototype miadi-prototype:miadi-factory-interface-analysis, two ceremony traces and its prompt; miadi-chronicle://550 and miadi-chronicle://140 hold their notebooks as nodes.
• The RISE text is 1.3.0: rise://jgwill/llms-txt/llms-rise-framework.txt@27cf18f, with the skill rise://jgwill/etc-claude-code/skills/rise-framework/SKILL.md@7e3e40d.
• The Author's Desk prompt miadiPrototype-authors-desk-storytelling-pipeline-261010 is at version 6: version 5 (EchoLune, ChatGPT) plus one block, "Prerequisites in implementation", naming the packages as published and what is next.
• The screenwalk prompt for the walk is screenwalk-261010-what-an-episode-holds-from-a-proposal-to-its-doors v1 in the Ceremony project, held here as miadi-tracing:ceremony/prompt/screenwalk-261010-what-an-episode-holds-from-a-proposal-to-its-doors@1.
• The sessions lane answered the steer in steers/261010-sessions-route.reply.md (ca864f3): A7 shipped as @miadi/hooks-interpreter 0.4.0; its F22 (699 of 939 binding lines name episode 103 through the declared fallback) is why the room reads through that join. A8 waits on Q2.

Where it stands (2026-10-14, afternoon)#

Guillaume's word of 2026-10-14, on the list of what could be done right away: "do what you can that has a high confidence and come back with the rest." Two decisions came with it.

• D-c is decided, differently from the proposal: the other Langfuse project will not be called Story. It is Creative, "simply because these are for what we create": stories will be in it, and more creative projects than stories. The tracing domain story is renamed creative everywhere the code and the docs named it (TRACING_DOMAINS, the CREATIVE_LANGFUSE_* keys the provider reads, the room's domain picker, the MCP tool's enum, the READMEs). No manifest in the chronicle carried domain: story, so nothing on disk is rewritten. The Creative project itself is planned, not created: until its keys exist the domain is not configured and the service answers nothing for it.
• Q2 of the sessions route is decided by absorption: asterion will be absorbed into Miadi, so the sessions routes stay in Miadi. A8 (the episode-facing sessions route) already stands as GET /api/chronicle/episodes/{ref}/sessions from A10 (jgwill/Miadi 30126b37); nothing more to place. The answer is in steers/261014-q2-answer.md.
• The review's deferred items are done: F10 (an artefact held by several episodes resolves for a viewer who may see any holder; the app reads the wheel's edges, since the ilex wheel ignores ?to=, and the tracing node's address no longer pins a version), F13 (a prompt id may carry folders, miadi/ep120-fork), F21 (the host workspace map is wired: /api/chronicle/resolve answers host.local_path for a rise:// address to a viewer who may write), F25 (framer-motion pinned to ^14.1.0; the lockfile changes by that one specifier). A12 is done early: the schema's deprecated observeEpisodeSessions copy is removed, since nothing outside the two packages imported it.
• Published: @miadi/episodic-memory-schema 0.16.0, @miadi/tracing 0.1.1, @miadi/tracing-langfuse 0.1.1, @miadi/inquiry-weave 0.17.4; the kit pin follows; :3335 rebuilt from main.

Left for later, named by the review#

Done 2026-10-14 (see "Where it stands" above): F10, F13, F21, F25, and the schema's deprecated observeEpisodeSessions copy (removed at 0.16.0). Still open:

• F15 made_by on a notebook names operator sessions to every reader while the sessions door treats them as writer-only: one reach rule to decide. Recommended: keep the agent handle public, strip the tmux name and the session id from public reads.
• The root manifest carries 55 more latest ranges (the v0 template's); each moves the lockfile on an unfrozen install, as framer-motion did. Pinning them is a dependency policy, not a fix, so it is named here and not done.

Pages the agents published#

A typed pages: list for such addresses is N9 on the proposal; until it exists this table and the references: line are the record.

Plot threads#

• What an episode holds — from two typed lists (reviews, foundations) to six, each walking the same four steps: a contract in the schema, a door in inquiry-weave, a route and a card in the app, a tool in the kit.
• The engine decides what is obvious — a proposal says what it would do before it is read; the first run put nothing above 0.8 and the go came anyway; the rulings on A1 and E7 are the first calibration.
• Two agents, one prompt — a terminal seat and a ChatGPT thread version the same Langfuse prompt; the human chooses the length (v2 at 21k was too much, v3 at 13.7k was right, v5 is EchoLune's).
• An address is not a location — the resource-addressing foundation applied: a notebook by its uuid, a prototype by its slug, a trace by domain and resource, a spec by repository and path; the doors say where each lands and for whom.

Beats#

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

• The name arrives from the work, not from the plan (2026-10-14): the proposal said Story; the project is Creative, because what goes there is what we create, and stories are one kind of it. A rename in the code took an hour; the word took four days of using it.

What needs Guillaume#

Decided 2026-10-14: D-c (the project is Creative, the domain creative), Q2 (Miadi; asterion is absorbed). Decided 2026-10-15: D-b, miadi-tracing: stays canonical and the short forms stay aliases, by the tracing-vocabulary seat under Guillaume's delegation of that day, recorded in foundations/tracing-provider-vocabulary/synthesis.md (Decisions, D1; jgwill/Miadi 870b731e); nothing changes in the code. A6 was done 2026-10-11. Still open:

• The rulings on A1 and E7 (E7: the RISE spec text itself).
• F15, the reach rule for made_by (above).
• N9, a typed pages: list; until then the proposal page stays under references:.

Lineage#

Episode 076 holds the Jev review and the inquiry this work is followed in; Episode 120 is the prototype's episode; Episode 550 set the screenwalk as a media type; Episode 551 is the loop that learns between sessions, which the scoring practice feeds.