Design record · The awakener plate · 2026-08-17

What a plate should take from a system map.

The awakener document arrived carrying its own drawing: 1200 × 760, three planes, fifteen components, 49 labels, and a panel that fills in a component’s contract when you click it. It is a good system map. The question this sheet answers is not how to reproduce it — it is what a plate on this site should draw, which is a different question and has a different answer.

The standing rule, from the A.3 entry in docs/HANDOFF.md: a plate does not restate the prose beneath it — it shows the form, and the prose explains it. A map that draws all fifteen components at equal weight restates the prose. It shows everything and therefore says nothing the text has not already said, at a size where the labels cannot be read.

Every string in these sketches already appears in src/content/design/awakener.md. Nothing here is written in the site’s own voice, and no component has been renamed except seat → station, which is Proteus’s ruling of 2026-08-17 and is already applied throughout the document.

Sketch 01 · The map as it stands, at the width it would occupy

Not a proposal — a measurement, drawn so it can be looked at rather than argued about. The source is 1200px wide and sets its component names at 15px and its detail lines at 11px. The document sets its prose in a 48rem column, which is 768px. Scaling 1200 into 768 is 0.64×, which puts the names at 9.6px and the detail at 7px.

Inside the prose column · 768px · source drawn at 1200

MESSAGE PLANE · DURABLE · AUTHORIZED · REPLAYABLE WAKE PLANE · EPHEMERAL · SIGNED · LOW LATENCY AGENT PLANE · RUNTIME-AGNOSTIC · FAIL-CLOSED Client MCP · HTTP · SDK Admission identity · schema · roster default deny Durable inbox message + thread read state · Tier-0 witness Tier router T0 voice · T1 vault T2 coordination · T3 herald Audit chain admit/refuse content hash Wake receipts v2 proposal Portable broker NATS adapter today Tier streams priority + retention Signed wake hint nonce · freshness 30s or less Wake daemon verify · cooldown Operator gate roster · activation Tier-0 ACK unpins inbox cursor Model runtime complete ≠ truncated am-dyad station known-tail gate ceiling · loop · echo fuse Runtime adapter AgentAPI · cmux

The finding It is not that the drawing is bad. It is that fifteen components at equal weight is a reference, and a reference wants the width of a screen and a pointer. Set in a reading column it becomes an illustration of complexity rather than a statement about it — and the document already lists every one of these components in prose, three inches below.

Sketch 02 · The path that leaves and comes back

One claim, drawn: the durable path is a spine and the wake path is a detour off it. The message reaches the tier router whatever happens. The wake path leaves there, runs through the wake plane and rejoins at the station — and if it is lost, the station still finds the message by polling. That is the delivery invariant, which the document asserts first and which prose can state but not show at a glance.

The topology is the document's, checked edge by edge rather than redrawn from memory. An earlier version of this sketch had the wake path leaving Admission. It leaves the Tier router — two lines, in the original — and the difference is the whole trigger: Maps InterruptAlert to Tier-0 Voice. Other schemas remain durable but do not fire the physical wake side channel. That version also invented a Complete turn box and hung the acknowledgement off it, where the original acknowledges from the station. Both corrected. A plate may show less than its document; it may not say something different.

Nothing here is pecked, deliberately. The first version drew the wake path broken to mean severable, while sketch 03 below and the rest of the site use a pecked line to mean not yet built. One mark, two meanings, on one sheet. The wake path is implemented, so it is drawn solid, and the claim that it may be lost is carried by the band label, the return line and the quoted invariant instead.

Full main column · 1134px

MESSAGE PLANE · DURABLE · MUST NOT BE LOST Client MCP · HTTP · SDK Admission default deny Durable inbox source of truth Tier router T0 fires the wake WAKE PLANE · EPHEMERAL · SIGNED · 30s OR LESS · MAY BE LOST Signed wake hint nonce · freshness Wake daemon verify · cooldown Runtime adapter AgentAPI · cmux AGENT PLANE · RUNTIME-AGNOSTIC · FAIL-CLOSED am-dyad station reads the inbox Tier-0 ACK signed outcome a hint, not the message until this returns, the cursor does not advance A lost wake hint may increase latency; it must never lose the durable inbox message.

What it omits, stated rather than left to be noticed Eleven of the original's nineteen edges and seven of its fifteen components. Gone: the audit chain and both edges into it, the operator gate and the failure line to it, the tier streams, the portable broker, the wake receipt ledger, and the model runtime's exchange with the station. Every one is still described in the prose beneath the drawing. What is drawn is not contradicted by the original; it is a subset of it.

For it It draws the argument rather than the inventory. A reader who looks at nothing else takes away the two things the document most wants them to have: the wake path is a detour, and the acknowledgement is a barrier rather than cleanup.

Against it It is not a map, so it cannot be used as one. A reader wanting to know where the audit chain sits will not find it here, and without sketch 03 the document has nowhere to send them.

Sketch 03 · Three planes, with what is not yet built drawn as not yet built

The map kept, but re-drawn at the column’s real width with the site’s own status convention doing work the source leaves to a colour key: solid is implemented, pecked is proposed or still being validated, brass is a human gate. The same convention the Observatory cards and the homepage chart use. It says what the source’s legend says, in the line itself, so the drawing survives being printed in one colour.

Full main column · 1134px

MESSAGE PLANE · DURABLE · AUTHORIZED · REPLAYABLE WAKE PLANE · EPHEMERAL · SIGNED · LOW LATENCY AGENT PLANE · RUNTIME-AGNOSTIC · FAIL-CLOSED Admission identity · schema · roster default deny Durable inbox message + thread Tier-0 witness Tier router T0 voice · T1 vault T2 coordination · T3 herald Audit chain admit/refuse content hash Tier streams priority + retention Signed wake hint nonce · freshness 30s or less Wake daemon verify · cooldown Portable broker NATS adapter today interface tomorrow Wake receipts v1.1 proposal Runtime adapter AgentAPI · cmux Station known-tail gate ceiling · loop · echo fuse Model runtime complete ≠ truncated Tier-0 ACK signed outcome unpins inbox cursor Operator gate roster · activation latch clear · abort

For it It is still a map, so it still answers “where does this sit”. And the status is carried by the line rather than by a colour key, which means it reads printed, it reads for a reader who cannot distinguish the source’s blue from its purple, and it agrees with the two drawings this site already ships.

Against it Thirteen components is still an inventory, and the delivery invariant — the thing the document leads with — is nowhere in it. A reader takes away that the system is large.

Sketch 04 · The original, embedded

Proteus: none of these look like the original layout — what about embedding an HTML display object in the page to render what Bodhi sends over? This is that, and it is the answer the site has already given once: on 2026-08-15 it took the position that it may quote someone else's drawing, presented as authored, with provenance stated on the page. The HAER survey on /architecture and /practice is that decision; an incoming design document's diagram is the same posture.

The SVG below is the author's, byte-for-byte apart from a unique marker id per copy. Its own stylesheet is reproduced scoped under a wrapper so it cannot reach the rest of the sheet, and its ten custom properties are supplied on that wrapper. No geometry, label or edge here is this repository's — which is precisely why it cannot misstate the design the way sketch 02 did.

04a · as authored, the author's palette

Ming-Qiao awakener component architecture Messages enter through MCP or HTTP, pass default-deny admission, persist to the inbox and audit chain, route by tier, and only Tier Zero emits a signed short-lived wake hint. A wake daemon verifies and dispatches to a runtime adapter. The dyad reads the inbox, applies safety brakes, invokes a model, replies, and explicitly acknowledges the Tier Zero alert. MESSAGE PLANE · DURABLE · AUTHORIZED · REPLAYABLE WAKE PLANE · EPHEMERAL · SIGNED · LOW LATENCY AGENT PLANE · RUNTIME-AGNOSTIC · FAIL-CLOSED ClientMCP · HTTP · SDK Admissionidentity · schema · rosterdefault deny Durable inboxmessage + threadread state · Tier‑0 witness Tier routerT0 voice · T1 vaultT2 coordination · T3 herald Audit chainadmit/refuse · content hashdrift detection Tier streamsdurable inbox deliverypriority + retention Signed wake hintam.wake.<target>nonce · freshness · ≤30s Wake daemonverify · cooldowndispatch adapter Wake receipt ledgerv2 proposalaccepted → dispatched → observed Portable brokerNATS adapter todayinterface tomorrow Runtime adapterAgentAPI · cmuxfuture: webhook / local runner am‑dyad stationpoll + known-tail gateceiling · loop · echo fusemodel harness · replyloopback /status + /health Model runtimeClaude · Kimi · localComplete ≠ truncated Tier‑0 ACKsigned outcomeunpins inbox cursor Operator gateroster · activationlatch clear · abort

Against it It is a foreign object on the page. Inter against Caslon and Rokkitt, a white ground against linen, and five hues that belong to no other drawing on this site. The HAER plates were brought onto the paper before they were shown — the scan's white was converted to transparency precisely so it would sit on the ground rather than on top of it.

04b · the same drawing, the site's palette and mono

Ming-Qiao awakener component architecture Messages enter through MCP or HTTP, pass default-deny admission, persist to the inbox and audit chain, route by tier, and only Tier Zero emits a signed short-lived wake hint. A wake daemon verifies and dispatches to a runtime adapter. The dyad reads the inbox, applies safety brakes, invokes a model, replies, and explicitly acknowledges the Tier Zero alert. MESSAGE PLANE · DURABLE · AUTHORIZED · REPLAYABLE WAKE PLANE · EPHEMERAL · SIGNED · LOW LATENCY AGENT PLANE · RUNTIME-AGNOSTIC · FAIL-CLOSED ClientMCP · HTTP · SDK Admissionidentity · schema · rosterdefault deny Durable inboxmessage + threadread state · Tier‑0 witness Tier routerT0 voice · T1 vaultT2 coordination · T3 herald Audit chainadmit/refuse · content hashdrift detection Tier streamsdurable inbox deliverypriority + retention Signed wake hintam.wake.<target>nonce · freshness · ≤30s Wake daemonverify · cooldowndispatch adapter Wake receipt ledgerv2 proposalaccepted → dispatched → observed Portable brokerNATS adapter todayinterface tomorrow Runtime adapterAgentAPI · cmuxfuture: webhook / local runner am‑dyad stationpoll + known-tail gateceiling · loop · echo fusemodel harness · replyloopback /status + /health Model runtimeClaude · Kimi · localComplete ≠ truncated Tier‑0 ACKsigned outcomeunpins inbox cursor Operator gateroster · activationlatch clear · abort

What changed between 04a and 04b Ten custom properties and the type face. Every coordinate, every label, every edge and every status class is identical — the two blocks are the same SVG. That is the whole size of the decision: the drawing is the author's either way, and the only question is whether it is shown in her colours or the site's.

What is lost either way The click-to-inspect panel. The author put tabindex on all fifteen nodes and data-node on each, so the interaction is keyboard-reachable and would survive being carried across — but it needs the document's script, which is a separate decision from embedding the drawing. Without it the nodes are inert, and the contracts they would have shown are in the prose.

The one that is not on this sheet

Both. 02 at the head of the document, where the argument is made, and 03 further down against What exists, what is being proven, what remains gated, where the reader has stopped being persuaded and started auditing. They answer different questions and neither answers the other’s. Two plates on one page is a cost, and the page is nine thousand pixels long — it can carry them.

Provenance, and what installing these would require

On the drawing Read from
Every component name and detail line the awakener document’s own body
The three plane descriptions Two planes, one durable truth
The quoted invariant in 02 Delivery. — verbatim, em dash and all
Which components are pecked the Status column of What exists…
Solid / pecked / brass the site’s own convention — ChartGround, the Observatory cards
station, never seat Proteus, 2026-08-17

Installing means one thing that does not exist yet. Every plate on this site derives its strings from the content module the prose is set from, so it cannot drift from the page beneath it. This document is Markdown, and a component cannot read strings out of a Markdown body. The map would need src/lib/content/awakener-map.ts holding the components and their status, plus a unit test asserting that the invariant the plate quotes still appears in awakener.md — the same guard the E.1 caption has against its intro. Without that, the first edit to the document leaves the drawing quoting a page that no longer says it.