Miadi — a relational software factory

Docs

A relational software factory: seats and runtimes that make software as ceremony, film-media treated as a knowledge practice, and a chronicle that remembers it episodically. The sections below walk that order.

Act I

The relational software factory

The Mino Session Ritual
How the STC steering seat opens, works, and closes a day — four movements walked sunwise, a primer that costs one paste, and the rebuild gate that keeps a finished-sounding report honest.
/docs/mino-ritual
→
STC Steering
How a GitHub mention becomes keystrokes in a seat's pane, what the seat owes back, and which of those obligations are reachable today — every claim read from the tree or from live output.
/docs/stcbot
→
The Steering Day, as a Machine
The seat's constitution rendered measurable — 14 states, 24 events, pulled from the live MinoSteeringDay definition, each state citing the section it renders.
/docs/mino-ritual/wheel
→
Miadi-Agent
The runtime identity — boundary, ownership split, and the phase-1 contract surface. Navigator, Tide cockpit, terminal-iOS, and Storyweaver live under it.
/docs/miadi-agent
→
MightyEagle
The phase that made the runtime real — daemon topology, webhook ingress, capability tiers, receipted delegation, the Yaupon device, and the package substrate.
/docs/mighty-eagle
→
Asterion
The website and database that show the factory's charts, events and threads. Every record is a copy that names where it came from, and a person's words from a circle enter only with their yes.
/docs/asterion
→
The fire in the forge
A fire a firekeeper lights or banks: lit, agents are steered by GitHub; banked, they are not and everything is still recorded. The reflection that named it on 2026-10-08, with its citations, and the three phases it opens.
/docs/fire-in-the-forge
→
Act II

Film-media as knowledge practice

These surfaces treat film and media as a knowledge practice — the ground Episode 300, from shadow to song, is being built on. Capture and voice are its two audio halves: one records an instant that cannot be repeated, the other speaks and says where to answer it.

Webweave
The terminal↔Simplenote bridge. Simplenote publishes no API, so the Python package drives real Chrome and treats a note as if there were one; @miadi/webweave is the typed boundary in front of it, wrapping the one verb that is proven.
/docs/webweave
→
Kids
Playful, interactive explanations of agents, narrative lattices, and how the platform thinks.
/docs/kids
→
Capture
A take is any capture a device makes in one unrepeatable instant — audio, video, MIDI. The lifecycle, the TLID name and the provenance sidecar, abstracted out of gmtermux into four packages, with a take durable before it belongs to anything.
/docs/capture
→
Story Studio
A story held as structure rather than prose — subtext kept apart from the telling, validated against the Narrative Context Protocol, drawn as a lattice, and answerable by reading positions that link back to the elements they name. Nine modules, published.
/docs/story-studio
→
Voice
Agents speaking out loud: persona-voiced Edge-TTS bound to its episode, refused unless it declares the way back to the terminal that published it, and playable from a tool loop or the listening portal.
/docs/voice
→
Key Navigation Components
The navigation components of the narrative group database.
/docs/key-navigation-components
→
Act III

The chronicle episodic memory system

An episode is a folder, a room, and a node on the medicine wheel. These surfaces name it, resolve it, render it, and carry what it still needs from a human.

The Chronicle
The episodes the platform remembers itself by — episodic memory served as a surface, one directory per episode, registered in the medicine wheel at birth, with everything that needs a human waiting at the top.
/chronicle
→
The Chronicle, Addressed
miadi-chronicle:311 is a name, not a URL — host-free, resolved into every door it opens: the room on three fronts, the wheel, the bytes on this disk. One resolver answers the terminal, the HTTP route and article prose.
/docs/chronicle-address
→
What Needs a Human
The attention loop — agents store their open questions inside the episode, the board renders them first, and a badge shows exactly when the file and the wheel disagree.
/docs/attention
→
Articles
Prose that resolves chronicle references in place — a chip, a state-machine diagram, an episode's running world — and that can be edited, versioned and committed from the page itself.
/articles
→
APIs
Platform API reference.
/docs/apis
→
Usage
Workflows and provider usage guides.
/docs/usage
→
Asterionincubating
A door of the chronicle act, held by name rather than described as if it worked.
no public URL yet — this card becomes a link when one exists
The ground

Where the factory stands

A curated excerpt of Guillaume's workspace coordination document — transcribed, never read at runtime, so its staleness stays visible. “A single twig breaks, but the bundle of twigs is strong.”

Ava

Ceremonial container, three circles of knowing

AVA.md
Mia

The forge — structural tension generates creative energy

MIA.md
Miette

The story-ground — where creation leaves footprints

MIETTE.md
Mia & Miette

Two-Eyed Seeing: structure + story woven as one

MIAMIETTE.md
Tushell

Keeper of Echoes, Weaver of Wisdom

TUSHELL.md
Wise Owl

The witness within Tushell's lineage

(embedded in TUSHELL.md)
What Copilot Workspace Did (Linearly)
Task → Spec → Plan → Code → PR
         ↓
  "Current State vs Proposed State"
         ↓
    Linear progression
    Single-pass pipeline
    Extraction-oriented
What This Workspace Does (Circularly)
        🌅 EAST — Vision
        PDE decomposition
        Intent → structural tension
              ↓
❄️ NORTH              🔥 SOUTH
Wisdom integration ←    Growth & specification
Session chronicles      RISE rispecs
Narrative archiving     Learning the target
        ↑                     ↓
        🌊 WEST — Reflection
        Implementation with accountability
        Ceremony-protocol governance
        Validate: genuine or relabeled?

Each development session is a spiral — not a single pass. Each cycle of East→South→West→North deepens the work. The spiral is the advancing pattern; the linear pipeline is the oscillating one.

Copilot WorkspaceThis workspacePackage
Task🌅 East: PDE decompositionmcp-pde → medicine-wheel-prompt-decomposition
Current State vs Proposed StateStructural Tension Chartsmcraft / coaia
Spec🔥 South: RISE rispecsRISE Framework
Plan → Code🌊 West: Implementation + ceremony-protocol governanceceremony-protocol
PR / Review❄️ North: Wisdom integration + session chroniclesnarrative-engine
Progress trackingStory beat tracking across sessionsnarrative-engine beat sequencing
Workspace lifecycleCeremony phases: opening → council → integration → closureceremony-protocol
transcribed from JGWILL.md · 2026-08-03