Implementation & Gap Report — The Author's Desk prototype against jgwill/Miadi#

For EchoLune's brief on miadiPrototype-authors-desk-storytelling-pipeline-261010 (read at v5, draft/latest; v4 compared). Measured on 2026-10-10 on gaia by Mia (Fable 5.1), session miadi-episodic-memory-schema-and-mw-261010, under jgwill/Miadi#769 and jgwill/miadi-orchestration-kit#80. Nothing was published or deployed for this report; the code named below is committed on main and runs on this host.

The human writes; agents support and echo. Nothing below changes that.

1. Verified: resolves, installs, imports, type-checks, answers at runtime#

2. Available, not yet integrated for this prototype#

• The public front has no CORS header on /api/chronicle/... (checked on miadi.sanctuaireagentique.com): the prototype reads those routes from its own server routes, never from the browser. That is the v1 rule already.
• 120 is ambiguous as an episode reference on this host (two folders carry number 120); the front answered 409. Use the folder name 2026-07-10-episode-120-relational-film-production-media-editor or miadi-chronicle://120 through the resolve door.
• The three new routes (/notebooks, /prototypes, /tracing) are on main and not yet on the public front: the production build (A6 of #769) carries them.
• @miadi/tracing and @miadi/tracing-langfuse are not published yet; until then the prototype keeps its own @langfuse/client read (its lib/episode-data.ts pattern) behind a TracingAdapter whose shape matches @miadi/tracing's TracingProvider.
• The new reference schemes miadi-notebook:<uuid>, miadi-prototype:<slug>, miadi-tracing:<domain>/<resource>/<id>[@v] are typed in the schema and held by Episode 120, but @miadi/reference-ui does not render them yet (next step on #769; the chips will resolve a notebook without its Google URL and a trace without a project id).
• @miadi/hooks-interpreter reads session traces on the Factory host; from Vercel the Agents roster has no source and stays DEMO until the Factory serves a read route for it.

3. Proposed adapters and packages (interface, dependencies)#

• EpisodePrototypeAdapter → thin HTTP over GET /api/chronicle/episodes/{ref}/prototypes (public) and the same with Authorization: Bearer <writer token> for editor. Shape: { id, title, url, made_with, source, commit, issue, relation, reads[], added, editor? }. No new package.
• TracingAdapter → @miadi/tracing's TracingProvider (getTrace, listTraces, getPrompt, listPrompts, getSession, listDatasets, listScoreConfigs, uiUrl), metadata only, with @miadi/tracing-langfuse as the implementation once published. Two instances: ceremony (read, Evidence & Traces) and story (write, opt-in, the desk's own sessions).
• EpisodeAdapter → GET /api/chronicle/episodes/{ref} plus the five list doors (reviews, foundations, notebooks, prototypes, tracing), each answering { episode: { path, number }, <kind>: [...], count }.
• ReviewAdapter → /review/<uuid>/json and ?v=N public; listReviews server-side with MIADI_REVIEW_API_TOKEN or seeded links without it.
• AttentionAdapter → read attention.json through GET /api/chronicle/attention; every state change stays an owner action through the Factory's own UI (no write from the prototype in v5).
• Reference rendering → @miadi/reference-ui with createRemoteResolver({ base: <Factory front> }); nothing on a page embeds a Langfuse project id, a notebook's Google URL or an editing URL (the resource-addressing foundation: addresses are persistent, resolution is a door).

4. Keep as demonstrations in v5#

Story tracing writes (no writer exists; keys exist), audience telemetry (none, by design until consent and retention exist), the Agents roster from Vercel, the Plot Threads two-timeline visual (the bridge's crossing report is real and can be LIVE; the drawing is DEMO), Chronicle cycles beyond what the five doors answer.

5. Decisions for the human#

• D-a Publish schema 0.15.0, inquiry-weave 0.17.0, @miadi/tracing 0.1.0, @miadi/tracing-langfuse 0.1.0 and rebuild the public front (A6 of #769), so the prototype imports the service and reads the three new doors.
• D-b One canonical tracing scheme: miadi-tracing:<domain>/<resource>/<id> (recommended, provider-neutral) with miadi-trace: and miadi-prompt: accepted as input aliases, or the two shorter schemes as canonical.
• D-c Story prompts (miadiStory-*, miadiWrite-*) move from the Ceremony project to the Story project when the desk starts tracing (O14 on the proposal page), or stay tagged inside Ceremony until then.

Prerequisites for the next prompt version (one short block to insert)#

Prerequisites in implementation (verified 2026-10-10). Read the Factory through its doors and render through its reference layer. Episodes: GET /api/chronicle/episodes/{ref} and /reviews, /foundations, /notebooks, /prototypes, /tracing (public for public episodes; a writer bearer adds a prototype's editor and a trace's provider page); refer to an episode by folder name or miadi-chronicle://<n> through GET /api/chronicle/open?uri=. Reviews: /review/<uuid>/json. Tracing: @miadi/tracing over @miadi/tracing-langfuse (ceremony reads, story writes on opt-in), metadata only. References: render every miadi-*: address with @miadi/reference-ui; never embed a provider project id, a notebook's Google URL or an editing URL in a page. Call the routes from your server, not the browser (no CORS on the front).