One command from a domain to a node the mesh can see and grade
Join the FlashyOS mesh in one command — scaffolds a charter, handshake, directory fragment and emit workflow, then verifies you pass L2 before it finishes. No account, nothing published.
The on-ramp, collapsed to a single command. It writes the four documents a node publishes — a charter that passes every static check, the flashyos/1 handshake, a directory/1 fragment, and the workflow that keeps them verified — then runs the real validators over its own output and prints whether you reached L2. Reaching the second rung of the ladder stops being a consulting engagement and becomes a call.
One command writes the four documents a node publishes — an AAO charter that passes every static check, the `flashyos/1` handshake, a `directory/1` fragment, and a workflow that re-checks L2 on every push gated to your default branch — plus a page explaining them.
Then it does what scaffolders usually only promise: it runs the real validators — `validateCharter`, every static conformance check, and `validateHandshake` — over its own output and prints whether you reached L2. The claim is checked, not asserted.
It publishes nothing and asks for no account. It writes files into your repo and verifies them locally; serving them at your domain, and everything after, is yours.
Installing it puts this command on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.
create-mesh-nodeThe scaffolder does not assert conformance — it runs the same validateCharter, static conformance and validateHandshake functions the estate runs, over its own output, and prints the verdict. The workflow it writes re-checks L2 on every push, gated per run to the repository’s real default branch. Verify it yourself with `npx @flashyos/conformance yourdomain.com` after you deploy, which checks the files are actually served.
Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.