← All packages
Connect · v0.1.0 · Apache-2.0

@flashyos/create-mesh-node

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.

npm create @flashyos/mesh-node -- yourdomain.com --email you@org.comnpm ↗source ↗

Why it exists

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.

What it refuses to do
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 that follows, is yours.

Use it

Join, and be told whether you conform
npm create @flashyos/mesh-node -- acme-robotics.com --email jo@acme-robotics.com
# ✓ L2 reached — the charter passes every static check and the handshake is valid.

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-node

The licence

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.

Keep reading

Join the meshThe conformance ladder
Also in connect
@flashyos/agent@flashyos/mcp@flashyos/create-mesh-agent@flashyos/llm-gateway