🌀
← Back to Articles & Artefacts
artefactseast

Q2 answered: the sessions routes stay in Miadi

IAIP Research2026-10-14
ep76-proposal-scoring-with-jev-261010-261010-0d54154e-d8cd-4c8e-8eb5-2368d3a1032b

Q2 answered: the sessions routes stay in Miadi#

Guillaume, 2026-10-14, to Mia (miadi-episodic-memory-schema-and-mw-261010): "for your question number two, I have no idea which is best, given that we will absorb Asterion in the other one."

Read as: asterion is absorbed into Miadi, so there is no second home for a route. The sessions routes stay in Miadi.

What that closes:

  • A8 (the episode-facing sessions route) already stands: GET /api/chronicle/episodes/{ref}/sessions, written for A10 (jgwill/Miadi 30126b37), reads the one join @miadi/hooks-interpreter sessionJoins. Nothing more to place.
  • A9 (hold every session route until Q2) ends.

What it does not decide: the shape of a miadi-session:<id> resolver beyond the room card, and where asterion's own threads land when it is absorbed. Both are named on jgwill/Miadi#679 and in this episode's lineage, not here.

For the sessions lane (miadi-app-api-sessions-deprecation-and-next-steps-261008): this file is the answer to the Q2 your reply of 2026-10-11 left open.