part 1 of the content AGENT

AGENTS.md -#

Agent Mia · Session ID: 29dc8963-4133-4861-9048-514e24f525ce · Session name: miadi-talking-circle-into-asterion-threads-coaia-narrative#

Written 2026-10-06. This session wrote the Asterion guide in jgwill/Miadi docs, with Mia's reading of the term "thread", and set it against the thread issues in miadisabelle/asterion.

What this session made#

• /docs/asterion (overview): Asterion as one app at three addresses (asterion.jgwill.com, asterion.sanctuaireagentique.com, asterion.tushell.com), a database of copies that each name their source, three sources feeding it one way, the routes it serves, counts seen signed out.
• /docs/asterion/coaia-narrative (the bridge): the package jgwill/Miadi consumes (coaia-narrative ^0.22.0) and Asterion reads. Covers the MCP server, coaia-narrative/writer and coaia-narrative/contract, the record kinds (imported live from the package, contract v2), the three ways a memory file reaches Asterion (the ingest door POST /api/ingest/coaia-narrative, the registry sync, by hand), and the mapping chart → tension, action step → action step, narrative beat → beat held by its chart, chart family with beats → thread of type chart-family. Also the four registered projects (coaia-agent, medicine-wheel, mino-triage private, ep060 private) and where Miadi already uses the package (lib/stc/issue-charts.ts, lib/stc/steer-charts.ts, lib/stc/chart-view.ts, app/api/stc/chart-memory/route.ts).
• /docs/asterion/threads (Mia's reading): threads across the Miadi factory, with the two definitions held side by side, a ceremony as a room, five statements per thread type, state vocabularies, the five things called a thread, Ada's fixture circle walked turn by turn, and the per-person consent gate.
• Proposed issues are kept as data in app/docs/asterion/_issues.ts and shown with a Proposed label and no number.
• Commits in jgwill/Miadi: 2ace82f9, 0e8f213a, both pushed to main. Live on :3335 in prod and at https://miadi.sanctuaireagentique.com/docs/asterion.

miadisabelle/asterion#20 · a thread is an ordered line of beats (D10, D11)#

• D10, held for Guillaume. "A thread is an ordered line of beats that a person can follow from where it opened to where it resolved. One source keeps it: a chart memory, a circle, or a seat." Short form: "a tension is what is wanted, a thread is what happened, in order."
• D11, held for Guillaume. Keep "thread" for the narrative thread only. Call the other four by their own names: issue (or inquiry), branch notes, session, comment thread. The alternative is to keep the word shared and always qualify it.
• Thread types with five statements each (kept by, opens when, holds, ordered by, resolves when): TT1 chart-family (live, 17 threads holding 96 charts, 3 public), TT2 ceremony (built for miadisabelle/asterion#11, none synced), TT3 seat-branch (proposed in miadisabelle/asterion#10). TT4 issue is Q3 there.
• Findings used on the docs page: F29 (a chart-family thread's page shows no beats, filed by this session as page finding F1), F30 (a thread has no state, opened time or resolved time), F31 (chart-family beats carry projection time in created_at, the time they happened is in metadata.timestamp), F32 (the word "thread" names five things in the factory), F33 (nothing links a thread to a chronicle episode).
• Open questions there: Q3 (is an issue and its comments a thread type), Q4 (episode link by inquiry-weave lineage reference in metadata, or by a column).
• Comment from the stcissue seat: the notes in miadisabelle/workspace .mino/threads/ are announcements and status notes, not in-session branches. Recommendation: thread type announcement, keep seat-branch for miadisabelle/asterion#10. Its INDEX.md state words are already in use: waiting, delegated, frozen, spec'd, partially fixed.

miadisabelle/asterion#21 · a thread is a concern a reader follows (D12, D13)#

• D12, held for Guillaume. "A thread is a concern that someone opens and a reader can follow until it resolves. It has a wanted result and a state, and one source keeps it: a chart memory, a circle, a seat, or a ledger. Its beats are what happened about it, in the order they happened, and one beat can belong to several threads." Short form: "a thread is what we follow; its beats are what happened about it, in order."
• D13, held for Guillaume. Six states for every thread type: emerging, active, resolved, deferred, blocked, superseded (from Mia's ledger), in place of open and resolved (A37 in miadisabelle/asterion#20).
• Origin (F34): Guillaume's correction on 2026-08-25 in miadi-chronicle://339, take 260825200731: "We open a thread on something. It's like a channel, we talk about it there, and when it's resolved we close it." Mia's model file: relationship-channel-thread-role-model.md in 2026-08-25-episode-339-relation-to-mia-on-mobile-devops/.
• F35: Mia's ceremony thread ledger miadi.ceremony-thread-ledger.v1 holds 16 concern-threads, a fourth source of threads.
• F36: a beat has one owning thread (narrative_beats.thread_id, migration 001), so two concerns cannot share a moment. A43 proposes a many-to-many beat_threads table.
• F37: Guillaume on 2026-10-06 proposed following a thread as a subscription, the thread as a topic (event-driven, connects to miadisabelle/asterion#9).
• Open questions: Q5 (is a chart family a thread, or the record a thread is kept in), Q6 (does a thread's topic carry beats or references to records kept elsewhere).

miadisabelle/asterion#22 · a ceremony is a room (D14)#

• D14, held for Guillaume. A ceremony is a room, not a thread. Its turns belong to a discussion, and its concerns are threads.
• Room (intention, integrates), discussion (ordered turns, open or paused, carries thread_refs), thread (concern that resolves, defers, blocks, splits or is superseded). Closing a thread never closes the room. Closing a room leaves each thread in its own state.
• F40: the definition in miadisabelle/asterion#20 describes a discussion exactly, and the noun is the one in question.
• F41: no ceremony has been synced into Asterion, so circle-projection.mjs can change its output shape before the first consented sync at no cost.
• Open question Q7: is the discussion its own table (narrative_discussions) or a thread type for the ordered line.

miadisabelle/asterion#11 · a ceremony held in a Miadi circle reaches Asterion with consent#

• Built and live on gaia: migration 001 (a beat can be held by a thread), circle-projection.mjs, circle-sync.mjs (plan, register, sync, list), private-circle visibility, /threads/<id> showing turns in order.
• Mapping as built: circle → project, talking circle → thread of type ceremony, closing record → the thread's closed_at, turn → beat of type turn held by the thread.
• Consent per person, read from the wheel, never written by Asterion or by an agent: grantor the person, grantee asterion, data type the circle id, purpose asterion-projection. The facilitator's yes carries the circle and its ceremonies, each speaker's yes their own turns, a witness is named only with their own yes. A withdrawn yes keeps the row and empties its words.
• Step 6 waits: the first sync of the one public circle circle:1790168517087:mtc50e needs Mia's yes as facilitator and Guillaume's as member. The wheel holds 0 consent records, and Miadi has no page where a person gives that yes.
• Questions carried on the docs page: Q1 (is an agent such as Mino a speaker who gives its own yes), Q2 (a turn posted by a seat for a person keeps both speaker and poster), Q3 (is a circle's diary part of its thread), Q4 (what closes a chart-family thread, which miadisabelle/asterion#20 answers as "the first chart completes").

miadisabelle/asterion#10 · seat-branch threads#

• Proposed type seat-branch: opens when a decision is put to William or a defect is found mid-session, resolves when the chart step completes or the person answers on the issue.

miadisabelle/asterion#12, miadisabelle/asterion#17, miadisabelle/asterion#19 · docs and absorption#

• miadisabelle/asterion#12 is the layers and docs proposal whose Threads segment is miadisabelle/asterion#20.
• miadisabelle/asterion#17: Asterion's own /docs is empty on every deployment. DP6 there is meant to open with the thread definition.
• miadisabelle/asterion#19: Asterion is planned to move into jgwill/Miadi. F27 there: jgwill/Miadi's issue charts (.coaia/jgwill-Miadi.jsonl) are the one chart memory not connected to Asterion.

Proposed issues (not filed)#

• PI1 (jgwill/Miadi): Asterion's docs have one home before the absorption, Asterion's /docs or Miadi's /docs/asterion. Relates miadisabelle/asterion#17, miadisabelle/asterion#18, miadisabelle/asterion#19.
• PI2 (jgwill/Miadi): /docs/asterion/threads states one definition once D10 to D14 are taken. Relates miadisabelle/asterion#20, miadisabelle/asterion#21, miadisabelle/asterion#22.
• PI3 (jgwill/Miadi): the docs name the five things the factory calls a thread. Relates miadisabelle/asterion#20 (D11).
• PI4 (jgwill/Miadi): Miadi's own issue charts reach Asterion as a private project. Relates miadisabelle/asterion#19, miadisabelle/asterion#9.

Findings this session did not act on#

• README of miadisabelle/asterion lists asterion.sancuaireagentique.com, which does not resolve. The address that answers is asterion.sanctuaireagentique.com.
• The Asterion card on jgwill/Miadi /docs still reads "incubating, no public URL yet" while all three Asterion addresses answer.

---

end part 1#