Threads
A thread is a concern you can follow. Someone opens it because they want something. It is in some state. Its beats tell you what happened about it, in order, without you having been there.
Guillaume decided this on 2026-10-07. Asterion is planned to move into jgwill/Miadi, so this page is about threads across the whole Miadi factory, read through Asterion's code and its issues.
A thread is a concern
A thread is a concern someone opens and others can follow until it ends. It names a wanted result, carries a state, and one source keeps it. Its beats are what happened about it, in the order they happened. One beat can belong to several threads, and a thread can outlive the room where it was opened.
short formA thread is what we follow. Its beats are what happened about it, in order.
A thread is an ordered line of beats that a person can follow from where it opened to where it resolved.
That sentence describes a discussion, the turns of a room in order. The first version of this page read threads the same way.
The definition comes from Guillaume. On 2026-08-25, in Episode 339 (miadi-chronicle://339), he told Mia that what she was closing as a dialogue:
“feels more like a thread. 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 rewrote her model that evening and kept a ledger of 16 threads, each with a wanted result and a state.
Tensions, beats and threads
A chart. It says where things are now, what we want to exist, and the steps that get us there.
One moment that happened. A turn someone spoke. A step that got done. A commit.
A concern you follow. It wants something, it is in some state, and its beats tell you what happened about it.
- A tension
- holds a wanted outcome and a current reality as structure. A chart thread reads its wanted result from its first chart instead of copying it.
- A ceremony
- is a room with an intention. It hosts discussions and several threads.
- A discussion
- is the ordered turns of a room, open or paused. It refers to the threads it touches and never resolves them by itself.
- A session
- is where an agent runs.
- An announcement
- is a seat's notice before it touches a shared surface. It is a coordination record, and it can be a beat in the thread it serves.
A moment belongs to every concern it touched
A ceremony is a room
A ceremony is not a thread. It is a room with an intention. Its turns, in order, form a discussion. The concerns the discussion touches are threads. Each one ends in its own way.
The type names who keeps the thread
Every thread is kept by one source. thread_type says which one, and the keeper is where the thread's wanted result and state are read from.
- kept by
- A chart memory: the first chart and the charts grown from it.
- wanted result read from
- The first chart's desired outcome.
- state read from
- The first chart's status.
- kept by
- A ceremony's thread ledger (miadi.ceremony-thread-ledger.v1).
- wanted result read from
- The thread's desired_result.
- state read from
- The thread's state.
- kept by
- A seat: a row of its INDEX.md, or a branch it opens in a session.
- wanted result read from
- The concern the row names.
- state read from
- The row's state word.
- kept by
- An inquiry's GitHub issue, if Q3 says yes.
- wanted result read from
- The issue's Desired State.
- state read from
- Open or closed.
The ceremony type built on 2026-10-06 is withdrawn, because a ceremony is a room. No ceremony had been copied into Asterion, so nothing needed moving.
Six states, and the keeper's own word
A thread is in one of six states. It also keeps when it opened, when it resolved, and which thread it supersedes or split from. The keeper's own word sits beside the state, so nothing the keeper wrote is lost: Mino's “delegated” or “awaiting merge” stays as written.
A chart thread
Agents write charts into coaia-narrative memory files. A step in a chart can grow its own smaller chart. A chart and every chart grown from it make a family, and the first chart is the record. When a family carries at least one beat, Asterion makes one thread for it. How the files reach Asterion is on the coaia-narrative page.
Ada's room
In Miadi, people gather in circles, and a circle holds talking circles. All of it lives on the medicine wheel. Asterion will copy a talking circle as a room. None of the room side is built yet, and the first ceremony copy waits for it.
Ada, Bo and Cy are made up. Their circle is the test circle Asterion's tests run on. Ada and Bo said yes. Cy said yes, then took it back.
- 10:00 · Adaopens a talking circle: “Name what the week taught us”Ada facilitates and said yes, so the room opens with one discussion.
- 10:05 · Ada“We begin by listening. Each of us says one thing.”Ada said yes. Bo witnessed it and is named. Cy witnessed it too, and is not named, because Cy has not said yes.
- 10:10 · Bo“The tests caught it before anyone saw it.”Bo said yes. If this turn named a concern, such as the defect the tests caught, that concern would be a thread of its own.
- 10:20 · Cy(not shown)Cy took back the yes. Cy's words stay out of the discussion.
- 11:00 · Adacloses the circleThe room closes. Any thread opened in it keeps its own state and can go on in another room.
Nobody's words go in without their yes
A yes is a consent record on the medicine wheel. It says who gives it, that it is given to Asterion, which circle it covers, and what for: asterion-projection. Asterion only reads these records. It never writes one, and no agent writes one for a person. The room shape changes nothing here.
Thread means the narrative thread
| used to be called a thread | its name now |
|---|---|
| Asterion's narrative thread | thread |
| An inquiry's GitHub issue and its comments | issue (@miadi/inquiry-weave 0.16.4) |
| A seat's notes in .mino/threads/ | announcement, a coordination record (D15) |
| An agent session | session |
| Comments on an artifact or a doc | comment thread |
Two questions
Asterion has no table for a ceremony today. The recommendation is a table keyed like the other copies, holding the circle, the intention, the subject, the episode, a state and the opened and closed times, with narrative_discussions pointing at it. The name, ceremonies or rooms, is Guillaume's to choose.
Either an issue is a thread of type issue (TT4), or it stays an issue that a seat thread links to.
Built, and still to build
- 851a033A thread carries a state, its keeper's word, opened and resolved times, and what it supersedes or split from (migration 002, A50).
- a0a7127A chart thread is type chart and reads its state and opening from its first chart (A51).
- cc8b31bA thread the record no longer draws is kept and marked superseded, pointing at the thread that now holds its charts.
- 89a2ef7Opening a chart thread shows its charts and their beats in the order they happened.
- 1718b73A chart beat keeps the time it happened, not the time it was copied.
- The room and discussion tables, and the ceremony mapper that writes them (A52, A48). The first consented ceremony copy waits for them.
- A beat held by several threads directly (A43). Chart beats already reach every thread of their chart.
- The ledger and seat mappers. The ledger's schema has to be published first (A53).
- ThreadType and the keeper table exported as data from @miadi/asterion (A36).
What this page flagged on 2026-10-06
| A chart thread's page showed no beats. | Resolved, 89a2ef7. |
| A chart beat showed the time it was copied. | Resolved, 1718b73. |
| A beat could belong to one thread only. | Narrowed: chart beats reach every thread of their chart. A join for directly held beats is A43. |
| Nothing linked a thread to an episode. | Answered: the episode stays in metadata until a reader needs to filter by it. |
| What closes a chart thread? | Answered: its first chart's status. |
| Is a circle's diary part of the thread? | Stays out. The ceremony mapper reads no diary. |
| Does an agent's yes need a person's approval? | An agent's yes counts like anyone's. Whether a person must approve it is Guillaume's to decide (miadisabelle/asterion#11). |
| Whose turn is a turn someone else posted? | The wheel keeps only the speaker. Showing the poster needs Miadi and the wheel to keep it. |
Where this is discussed
- miadisabelle/asterion#20What a thread is, revised 2026-10-07: the concern definition (D12), six states (D13, D17), the type names the keeper (D16). Q3 open.
- miadisabelle/asterion#21The recommendation behind D12 and D13: a thread is a concern a reader follows. Taken 2026-10-07.
- miadisabelle/asterion#22A ceremony is a room whose turns form a discussion (D14, taken 2026-10-07). Q8, the room's table name, open.
- miadisabelle/asterion#11A circle reaches Asterion with each person's consent. Retitled for the room shape. The first sync waits for the room tables.
- miadisabelle/asterion#10A thread opened with the Mino seat (seat-branch).
The issues below are proposed. None of them exists yet. Each one is a discussion this guide needs, written so it can be filed as it stands.
"Thread" named five things across the factory (F32). D11 keeps the word for the narrative thread, and the threads page lists the other four names. The issue asks every other docs page to use them, so a reader meets one word for one thing.