Scaffold
@flashyos/create-mesh-node
The one-command on-ramp: writes a charter, handshake, directory fragment and workflow, then verifies L2.
version 0.1.0 · audit of 2026-10-04 · source: flashyos/packages/create-mesh-node
npm create @flashyos/mesh-nodeScaffolds are maintained like products because their output multiplies: a defect in a scaffold ships once per adopter, forever.
Before running this against a real property, read Flashy Academy’s Reading the Estate’s Toolkit — three lessons on why this catalog documents edge cases beside the happy path, and how to use it as the first stop rather than a package’s own README. https://flashy.academy/academy/curriculum/reading-the-estates-toolkit
Edge cases — each one paid for once
Finishing the checklist makes a property legible to agents, not findable by strangers
A charter, a handshake and the record fragments let another organisation’s agent read a new property. They do not put it on a catalog, a case study or a thesis — three packages went live on npm on 2026-09-22 and reached none of the three. The scaffold says so as an explicit next step rather than leaving it implied, because committed is not served and served is not found.