The Chronicle, Addressed
An episode is a folder on a disk, a room on three fronts, and a node on the medicine wheel. miadi-chronicle:311 is the name of that one thing — host-free, so the same reference reads correctly from this host, from the tailnet, or from the public front. One resolver turns it into every door it opens, and the terminal, the HTTP route and article prose all ask that same resolver rather than each keeping a parser of its own.
One reference, every door
inquiry-weave resolve prints the doors as a row of brackets, each its own OSC 8 hyperlink, with the canonical reference visible beside them — the OSC 8 specification says a hyperlink “should not be the only means of figuring out the target”, and there is no way to detect whether a terminal supports one.
$ inquiry-weave resolve "miadi-chronicle:311/services-inventory" écoute factorisation logiciels — the relational software factory [room·local] [room·tailnet] [room·public] [wheel·captures] [wheel·graph] [wheel·node] [wheel·relations] [file·inventory] <miadi-chronicle:311/services-inventory> episode 311 · 2026-08-05-episode-311-coute-… · matched by number path: /srv/miadi/episodes/…/services-inventory.json modality: relational
Where a human click should land — the episode room. An earlier draft returned only the file, and clicking it opened a text editor on raw JSON.
The bytes on this host. Local-first is about data ownership and availability, not about presentation — so the two answers are never collapsed into one field.
modality is the third answer, and it is printed on every human-readable run: a discretised harvest report in Fox & Brewer's sense — relational when the reference reached what it named, standalone when an artifact was asked for and not found although the episode resolved. HTTP shipped this field once as RFC 7234's Warning header and RFC 9111 obsoleted it for never being surfaced to users; a modality nobody renders is dead metadata within two releases.
| Flag | Does |
|---|---|
| --json | The full result: canonical, resolution, artifact, destinations[], open, shareable, path, modality. |
| --base local|internal|public | Lead with one door. Reorders; never removes one. |
| --local | Lead with the file on this disk. |
| --verify | Ask the wheel whether the episode is really on it. |
| --raw | No escape sequences — clean capture for scripts and CI. |
One resolver, three consumers
The parser and resolver moved into @miadi/inquiry-weave — the package that already ships built ESM, a bin, the catalog builder and the root precedence rule — so §7.1 of the spec stops living inside whichever of the three consumers happened to need it first.
Rootless, and why
Rootless. This is what every producer emits.
Normalized away on parse. `//` is RFC 3986 §3.2's authority marker, so a conformant parser reads the first segment as a host — new URL("miadi-chronicle://126") yields host "126" and an EMPTY path.
A trailing slash is an empty final segment in RFC 3986, and people type it by reflex. Refusing it degraded the reference in an article to raw braces with nothing explaining why — earned 2026-08-15 on episode 103.
Producers emit rootless; parsers accept both, forever. The reserved //root@…/ growth slot the spec kept was unreachable while episode data occupied the authority position.
Artifact segments
A reserved segment in the last position names an artifact inside the episode — and it is a registry, not a constant compared by ===. The tail is stripped before the episode is matched, so the reference resolves its episode either way. mc.show= is the second, independent trigger; the segment wins when the two disagree.
| Segment | Kind | Served by | Note |
|---|---|---|---|
| services-inventory | inventory | the vessel | services-inventory.json — an episode's running world. |
| state-machine | state-machine | the vessel | The diagrams/ convention smcraft's rispec 78 calls proven, falling back to smdf_files in services-inventory.json. |
| captures | captures | the medicine wheel | GET /api/captures?episode_path=<folder> |
| recordings | captures | the medicine wheel | Deprecated alias on the wheel — same records, older name. |
| inquiry | inquiry | the medicine wheel | GET /api/inquiry-weaves?episode_path=<folder> |
| plans | plans | the medicine wheel | GET /api/plan-perspectives?episode_path=<folder> |
episode_path — the full folder name. Measured 2026-08-16: ?episode_number=320 returns 0 records for an episode whose ?episode_path=<folder> returns 1, because the records carry no episode_number field and the filter compares strictly.Which fragments are spellable
State names are unique tree-wide (SMDF's V002), so they survive structural motion — a sibling insert cannot retarget them.
Addressed positionally. A sibling insert silently retargets the reference, and silence is the defect.
Name-keyed fragments are durable against structural motion and fragile against rename: SMDF's V002 gives uniqueness at a point in time, not immutability. The rename policy is named and pending (alias-table-pending) rather than assumed away.
A 200 proves nothing
The wheel's /graph, /nodes and /relations pages all begin "use client", and so does forgewright's chronicle view. The HTML shell is byte-identical for any parameter — focus happens in the browser, after it fetches /api/nodes. Measured 2026-08-16: ?episode=9999-99-99-episode-000-nope answers 200. Two services, two codebases, one trap.
GET /api/nodes/<id> discriminates — it returns the node or a real 404. That is what --verify asks, and it stays opt-in because it is a network call: a resolution answered from the catalog on disk is already true about the disk. Both answers are real, and they can disagree.Unreachable is not absent. A wheel that cannot be asked has not said no — the verdict carries the error rather than reporting the episode missing.
Clickable references: desktop, Terminator, tmux
sudo apt install miadi-terminal miadi-terminal front https://<your Miadi> # when MIADI_URL_BASE is not already it miadi-terminal enable # per user: desktop, terminator, tmux
Restart Terminator, then Ctrl+click a miadi-chronicle: reference anywhere in its output. In tmux, a click on the reference opens it, with set -g mouse on; on Termux that is a tap, from the Termux build of the same package. miadi-terminal status says what a click opens here, miadi-terminal disable reverses it. Running enable twice is safe.
An OSC 8 hyperlink calls open_url(prepare=False) and goes straight to xdg-open; only a regex match calls prepare=True, the sole path that consults url_handler plugins. The plugin covers what OSC 8 structurally cannot: a bare reference in output that knows nothing about miadi.
A click builds <front>/api/chronicle/open?uri=… and the browser follows the server's redirect to the room. The client holds no catalog and runs no node, so the same click works on a laptop, on a phone and on the host itself. The front is MIADI_CHRONICLE_OPEN_URL, else MIADI_URL_BASE, read through miadi-config at click time — nothing is baked in at install.
The same reference, in prose and over HTTP
GET /api/chronicle/resolve?uri=<url-encoded> — the whole URI travels url-encoded so its #fragment survives HTTP. A parseable-but-unknown episode is a 200 with resolved:false: a broken reference is data, not a server error. Missing or invalid input is a 400 carrying a usage document, so the endpoint describes itself.
In an article, the same reference written as a directive — {{ miadi-chronicle:311/state-machine }} — renders as a chip, a diagram card, or an inventory, resolved server-side. The + chronicle ref helper in the article editor drops the directive for you.
{kind, name, path, exists} — resolve, then hand the path to an editor or a canvas.