Measured answer: jgwill/Miadi — specifically packages/hooks-gateway. The deployment, not the types.

The typed spine exists and is real: @miadi/hooks-core@0.5.0, 12 source files, 14 tests. It is not wired to nothing — packages/hermes-conductor/src/hooksSink.ts imports appendJsonl/ensureSessionDirs, and packages/hooks-gateway/src/{server,worker,ledger,sink}.ts all import HookEventEnvelope.

But the running app imports it nowhere. Every hit under app/ is prose about it — app/docs/mighty-eagle/{ingress,substrate,delegation}. And the repo already says so in its own diagram: app/docs/mighty-eagle/substrate/_diagrams.ts labels @miadi/hooks-gateway 0.1.0 · not deployed.

So the aspect does not refactor a package that is missing. It refactors the distance between a tested spine and a serving surface — package-to-package wiring with nothing the platform actually serves at the end of it.

Counter-argument: hooks-gateway is 5 source files and 1 test at 0.1.0. Choosing it may be choosing the least-built thing because it is the most visible hole, when Observability-as-provenance might belong upstream in hooks-core's envelope before anything is deployed at all.

🧠 Resolution instance, dated 2026-08-08 — episode 317 (songbird — the phrase you sang stays) enacted this aspect rather than arguing it: the sung phrase is kept as voice (captured), transcribed to notes (derived), saved into the composition — lineage preserved end to end. The proof of stewardship: four months of MIDI was short by one hop (~46 ms, since gmtermux 6a063c1), and it is recoverable only because the voice was kept — the oral history made the repair possible. Deploy receipt from the android perch: SONGBIRD-DEPLOY-OK 10b8620 200 302; miadisabelle/gmtermux#50 closed with the record. Inquiry woven: ep317-songbird-deploy-resolution, registered on the chronicle wheel; lineage edge 317↔311 authored both shores.

🌸 Observability here wasn't a dashboard — it was a kept breath that let four silent months be repaired.