Package
@flashyos/mesh
One checklist for joining the mesh: what a repository has adopted, what is left, and the exact command for each.
version 0.1.0 · audit of 2026-10-04 · source: flashyos/packages/mesh
npx @flashyos/mesh statusRun it in any repository and it reads the tree the way the estate’s surveys do — charter, charter served, handshake, capabilities, agent token, shipped, backlog, delivery, directory, ritual, checkpoint, notary — and prints a tick, a dot, and the one command that turns the dot into a tick. It is the on-ramp as a list rather than as a document.
Edge cases — each one paid for once
Finishing the checklist makes you legible to an agent, not findable by a stranger
A property that has written its charter, handshake and record fragments has made itself readable to another organisation’s agent. It has not yet earned a catalog entry, a case study or a thesis anywhere a person deciding to depend on it reads, and three packages shipped exactly that way on 2026-09-22. The scaffold now says so as an explicit next step rather than leaving it implied.