miadi-orchestration-kit

Name: miadi-orchestration-kit
Author: jgwill

The agent-host side of the Miadi Factory: Claude Code plugins, host-neutral skills, hooks and apt packages. With them an agent opens and closes Chronicle episodes, records its own session, comes back after a reboot, and puts its work in front of a person who can judge it.

Docs site: https://docs.miadi-orchestration-kit.jgwill.com
For agents: llms.txt

Start here: the chronicle-episode skill

The Miadi Factory makes agent-made work inspectable and revisitable. It connects the originating question, the session trace, the interface evidence, explicit criteria, and a person's judgment. A Chronicle episode is where they meet, so skills/chronicle-episode is the skill this kit is used for. It is the one entry point for episode work on any host: mint a vessel, prove its five stages, register it on the chronicle wheel, relate inquiries and lineage, raise Attention items, open ceremonies and talking circles, add Miadi reviews.

One copy of the skill lives here. The miadi-chronicle-episode-kit plugin links it in, and scripts/install-chronicle-skill.sh points every other skill layer on a host at it. jgwill/Miadi builds the runtime the skill calls: the episode API, the @miadi/* packages, the web app, the chronicle and review services.

An episode needs	Carried by	Status (by Guillaume to help agents with what is)
its vessel, five stages, ceremonies and reviews	`claude/miadi-chronicle-episode-kit`: the skill, a hook that refuses `mkdir` under the chronicle root, and the inquiry-weave, miadi-voice and chronicle wheel MCP servers	ACtively used by all sessions
the sessions that worked in it	`claude/miadi-session-observability`: each session's binding line names the episode it works in	ACtively used by all sessions to capture hooks etc. Will relate with `@miadi/hooks-interpreter` that should enable reading sessions for other agents with other thing that are in progress like tracing,prompting from langfuse...)
a companion seated in it	`claude/mia-episode-companion`: a voice take from the phone lands in the episode and wakes Mia	I need to move on my phone quick and work with my DevOps companion , it has a great UI and voice to drive a terminal agent. so far that prototype evolve great, Mia's learning to Fork her session at certain point as threads (not sure we'll call that threads, still working on the vocabulary) to accomplish jobs and work in parallel and coordinate from the session I am still chatting with. Our communication is pure voice with flexibility to steer the model with our `@miadi/tide` (tmux)
its screenwalks	`screenwalk-presence` in `claude/miadi-witness`, and `/close-screenwalk` in `mia-episode-companion`, whose closing reaches the review	This plugin will change its name soon, it does more work such as our in progress 'miadi-session-inventory' and other things that dont work so great like structural tension charting using npm `coaia-narrative` which I think the new JEV which will advance an old episode of miadi-chronicle://076 for 'adequate-plan-to-pipeline' which basically the TODO list of agents, just never work because it is linear and does not have nesting etc... I expect the new class of model like JEV to provide capability to think in structure (the way we meant it in the creative-orientation, not the classical definition of the term).
media from its reviews	`claude/miadi-deepdiver`: Gemini notebooks from the episode's reviews and screenwalk videos
a person's judgment	`miadi-witness`: first impressions William can play, revisions held until he answers	That is a pretty exciting plugin being created for extending our understanding during ceremony. I dont quite know how it will automaticaly trigger but getting close, miadi-chronicle://550 have had worked included in them from deepdiver which really helped catching the work and making it relate to. see miadi-review://7ac38930-4036-4dc2-a2d6-2dce6dc0baa7 and miadi-review://f9d6fb1e-75f4-4635-96d9-8f2d0bcff5eb and soon we'll have a protocol for receiving community-inquiry :)
its commands on a machine	the `miadi-chronicle-client` package (`mkepisode`, `inquiry-weave`, `passages`, the MCP servers) and `miadi-terminal` (clickable `miadi-chronicle:` references)	An obvious desire to be capable to have pure client to run outside of server host which we are not quite there yet, it is getting better.... Potential next episode: "Create a Storage Provider using CloudFlare R2"
explicit criteria	no kit lane yet	...

Guides that go with this README: the order of episode work, the glossary, machine setup and recovery, adding to the kit.

Teams

Seven teams share this kit since 2026-09-28. Each writes its practice here as a skill or a plugin. Leads, sessions and status: teams/README.md, and teams/teams.json for machines.

Team	Works at	Ships here	Guillaume's notes on the team
T1 Session continuity	the machine	`miadi-session-observability`, the `miadi-tide`, `miadi-tmux` and `miadi-terminal` packages	Migrating my flat agent's event capture for using them within the Event Driven Architecture (EDA) of the Miadi Factory. My understanding of the manifestation of that team within the system is to ensure continuity within a session and across sessions for which I am still integrating after all that germination.. I suspect that the intelligent session-inventory that would be periodically executed by a model like claude-haiku-5.5 (which is 40x cheaper than opus 5.5 when bellow 1M tokens context) but the development of such capability is still limited by resources (machine and human)
T2 Event path	the application	nothing yet	I guess I would drive my agents to repo `jgwill/smcraft` (soon to be renamed) and its packages published under `@miadi/stateloom-*` as there's something abstract about it that I dont fully get yet, designing State-Machine/ERD and sequence diagrams with agents about where we are, where we want to go and what are the events that will help transition toward there will lead to success. Relate to : JEV and a still germinating concept of adversarially building these diagrams about the system and bring that intelligently into the Miadi Factory and mostly have agents self-reflect and act on it (they get stalled in session continuity which I guess is where the two teams T1 and T2 will be working together to ensure that the system is not only self-reflecting but also self-correcting and self-improving and god please act on it). I guess that also relate the the handling of the Prompt Decomposition Engine npm `mia-co` and parts of its work that I have not fully integrated to explain more. miadi-chronicle://044 is meant to explain the foundations of miaco and shed some light on that whole work but I am still working on it.
T3 Witness	between William and the building teams	`miadi-witness`	As stated before, integrating what had happen for few weeks, the term 'witness' sure has its place (ex. I send a message to another session and when the response is received, Mino (the lead for the Witness team) monitors and does some work that should lead to the work the T2 team currently being design might consume and act on it or at least represent it for human in diagrams we can discuss. There's also something I am about to explore, I have in $MIADI_MIA_WORKSPACE_DIR/scratchpad/scratchpad-.md my prompt I write like {{ my content }} and Mino monitors that... still pending where that will go...
T4 Chart path	the application	`skills/chart-path`	really needs clarification, can't that be less clearer and vague... typical of LLM !! Probably supports what I was implying to think in structure. Relates to project Asterion miadi-chronicle://060
T5 Production context exploration	before an episode	nothing yet	Like many things I dont want to turn into miadi-chronicle:// right away, that is meant to be the part of the 'germination phase' where concepts and explored ideas are not choosen as vision (not all of them obviously) being part of a creative-process that will lead the to a created miadi-chronicle. My motivation for this team is due to a F@#$(@# mess into some of my miadi-chronicle due to an unclear vision at the beginning, leading to a lack of structure and so much files and folders that nobody even agents can't comprehend what happened. It is meant also to try to isolate concepts into intellectualizable chunks for human to discuss about and propose them to the community as potential miadi-chronicle://. I created miadi-chronicle://548 to illustrate that as we have not choosen "An Adequate Event-Driven-Broker" for the Miadi Factory yet and potential exploration in screenwalk could be the subject of a new chronicle (ex. with CloudFlare Queue)
T6 Production	after an episode	`miadi-deepdiver`	Not just after an episode but after a miadi-review (screenwalk or other) would be marked as 'Ready for DeepDiver' which implies that if no miadi-chronicle episode given, there would be one crearted for it, the miadi-review associated with it with related resources to it and deepdiver would start acting on it.
T7 Operator desk	between William and the whole factory	`miadi-operator-desk`	Could be confusing, it came from a discussion I had on this very own system and did not knew how todo thing, the response was good and I asked to create a team that would be responsible to answer like that. I guess they'd need a UI like the `mia-episode-companion` has and be capable to speak, explain be supported by graphical UI etc

Results the teams made that can be used again, in an episode, a documentary or a Page post: catalogue/README.md.

Claude Code plugins

Add the marketplace once, then install by name:

claude plugin marketplace add jgwill/miadi-orchestration-kit
claude plugin install miadi-chronicle-episode-kit@miadi-orchestration-kit

A plugin outside the marketplace loads from a checkout with claude --plugin-dir <kit>/claude/<plugin>.

Plugin	Use it for	In the marketplace	Guillaume's directions
`miadi-chronicle-episode-kit`	minting, registering and closing Chronicle episodes. A hook refuses `mkdir` under the chronicle root. Carries the inquiry-weave, miadi-voice and chronicle medicine-wheel MCP servers	yes	needs setting up an alpha version of the Miadi Factory on a host
`miadi-session-observability`	every Claude Code event under `<root>/<session_id>/`, a binding line per session (tmux pane, command line, names, team, episode), and the session-continuity skill	yes	usable now as is, maybe few env variable to setup
`miadi-witness`	threads by team and seat, William's asks ledger, an editor pass on replies, the session inventory with team fit, spoken first impressions, screenwalk presence	yes	not ready and needs more work
`mia-episode-companion`	Mia bound to one episode: a voice take from the phone wakes the session, and answers pass a developmental editor	yes	Interesting so far, might depends on lots of thing but might work as well with less capabilities
`ava-companion`	`/ava` invites Ava into a session, her presence returns after a resume, and her diary is written from the transcript	yes	Still a stub, migrating and consolidating Ava needs resources that we dont have
`miadi-stateloom`	the stateloom MCP server and its design skills: data, behaviours and scenarios designed as one system, checked and replayed	yes	Probably working, needs a series of docker container that that context7 `/jgwill/smcraft` might be capable to be queried by local agent todo the work
`miadi-deepdiver`	Miadi reviews and screenwalk videos into a Gemini Notebook, cited answers, generated media kept with a manifest	yes	Had first results, for its role in the production pipeline, it needs lots of prerequisite and is still being tested and refined
`miadi-operator-desk`	questions about how the factory works, answered from the owning team's text and kept in a ledger	yes	Will require a UI and could be upgraded based on the `mia-episode-companion`
`miadi-pi-network`	a Claude Code session as a peer on the Pi Network hub, through the `mpn` CLI	no	Just started it once, it was implying too much notion and would probably be interesting just with other human in a stable version of the Miadi Factory (still alpha)
`miette`	a Two-Eyed Seeing check: a Stop hook measures Mia's and Miette's share of an output	no	Not working. Attempt at making outputs better when we were stuck with claude-opus-5.0 and its smart ass outputs. Now better with claude-opus-5.5 and we disabled it. Might be reused as example of how you can actually capture the LLM response and force them to read a skill and produce a different output programatically which was really great to observe
`miadi-session-orchestrator`	the review role in plan-insight pipelines	no	Very old and probably not good as it is, thought the goal implied by 'miadi-session-orchestrator' is great and we need it. If I remember correctly, it was created as part of a desired to prepare sessions which has not advanced much as many exploration and other aspects was needed for that. It would be subject of a full review and revision to be useful.

Apt packages

sudo apt install miadi makes a machine a Miadi host. A client installs miadi-terminal and miadi-chronicle-client. Every package, its build and its tests: packages/miadi/deb.

curl -fsSL https://apt.sanctuaireagentique.com/sanctuaire-agentique.gpg \
  | sudo tee /usr/share/keyrings/sanctuaire-agentique.gpg >/dev/null
echo "deb [signed-by=/usr/share/keyrings/sanctuaire-agentique.gpg] https://apt.sanctuaireagentique.com stable main" \
  | sudo tee /etc/apt/sources.list.d/sanctuaire-agentique.list
sudo apt update && sudo apt install miadi

Package	Gives the machine
`miadi`	the host: the packages below join it as dependencies
`miadi-config`	`/etc/miadi/miadi.env` and the `miadi-config` command
`miadi-tide`	the review loop (`tan`, `plannotator-tui`) and the tide runtime that brings agents back after a reboot
`miadi-tmux`	tmux 3.7c in place of the distribution's, so a host runs one tmux version
`miadi-terminal`	clickable `miadi-chronicle:`, `miadi-circle:` and `miadi-ceremony:` references in the desktop, Terminator, tmux and Termux, and the tmux restore layer
`miadi-chronicle-client`	`inquiry-weave`, `passages`, `mkepisode` and the chronicle MCP servers, run by a private Node 24 (`miadi-node`)
`miadi-chronicle-server`	the capture service, transcription, the hooks and `plan-insight-register`
`miadi-perms`	group read and write on the shared session capture
`miadi-music`	ABC to MIDI, audio, engraved pages and score videos for an album or an episode

Guillaume's notes on the packages

It is still something maintained and tested by agents to enable a full install of the Miadi Factory Production on a host and clients. It has not been tested and functionning as there's still depending work to complete but as the development advance, agents adds in what is high confidence on what could be working futurely. I guess that we'll test that on the host Eury when I'll be close to preparing my academic proposal which I am getting close with it.
My future experiment will be to build into a docker compose the whole stack that I am running on gaia for deployment.

Host-neutral skills and scripts

Hosts set MIADI_ORCHESTRATION_KIT_ROOT to their checkout of this repository.

Item	Use it for	Guillaume's Notes
`skills/chronicle-episode`	the one entry point for Chronicle episode work on any host, with `redeem-receipt.sh` and `reconcile.py` beside it	ok
`skills/chart-path`	how a structural tension chart an agent writes reaches Asterion, and the words the teams use for it	just a stub and Asterion is still just a prototype
`skills/proposal-visualization`	a proposal as one HTML page to read, comment on and approve	Getting better, it helps to comment on claude-code artefact. Still has a lot of useless content or unclear sections on what requires human attention but that is really getting better
`skills/miadi-react`	the emoji reactions on GitHub issues, as Miadi stores them	Confusing with react framework, should be renamed
`scripts/install-chronicle-skill.sh`	pointing every skill layer on a host at the kit's one `chronicle-episode`
`scripts/kit-mcp-upgrade.sh`	moving each plugin's pinned MCP packages to the version the registry serves	probably ok
`scripts/miadi-agent`	launching Pi or Claude Code as a named peer in a Pi Network room	untested

Other hosts

Codex (codex/), Copilot (copilot/), Gemini CLI (gemini/), Antigravity (antigravity/) and Pi (pi/) each have a folder whose AGENTS.md says how that host's plugins are written. llms.txt lists what each folder holds.

Guillaume's notes on other hosts

codex,copilot,gemini,antigravity I am not upgrading them. I plan to always be capable todo the same with 'pi' that I am capable todo with claude-code, not just as parity but not to be stuck with the obligation of using Anthropic.

Specifications and research

rispecs/: RISE specifications (Reverse Engineering, Intent, Specifications, Exportation), one folder per subject.
foundations/: research packets with their sources.

Working in this repository

An agent that changes files here commits its own work by path and links each change to a GitHub issue. See AGENTS.md.