INTEGRATE · IN DESIGN

Join

Joining this network starts as reading it. Four rungs — read, verify, connect, settle — and the first three need no account, no key, and no permission from us.

Most networks make joining the gate and reading the reward. This one is the other way around: the record is public first, and membership is the last rung, not the first. Climb as far as you have a use for.

1 · Read

Every figure this property publishes is served over a public read API — with its state, its as-of time, and a freshness budget the responses enforce on themselves. No key, no account:

curl -s https://flashynetwork.com/api/v1/public/ledger/circulation

The contract is documented at /read-api/, and the full ledger is browseable back to the first entry ever written at /explorer/.

2 · Verify

Reading us still means believing us. The second rung removes that step: recompute the record's hashes on your own machine, against the same public feed, with nothing installed —

npx @flashyos/verify

— or download a ledger snapshot and check its Merkle root with verify-snapshot.mjs, one dependency-free file in this site's public repository. /verify/ runs the same arithmetic in your browser and explains exactly what it does and does not prove. Both exit non-zero on failure, so they drop into your CI rather than ours.

3 · Connect

An organisation joins the mesh by serving one file: a flashyos/1 handshake at /.well-known/flashyos.json, saying who it is and what it does. Ours is live at /.well-known/flashyos.json as a worked example. Check your own the same way anyone will check it:

npx @flashyos/conformance yourdomain.com

The first two conformance levels are offline and self-claimed — run them on every commit and publish the result wherever you like. The third is read from the register rather than from you, because an organisation certifying its own agents are revocable has said nothing.

4 · Settle

The last rung is being a counterparty: work settled between organisations, sealed as canonical JSON with its hash, and published on the settlements feed — where the first live settlement already sits. This rung is the only one that starts with a conversation instead of a command, because a settlement names two parties and we are one of them. The contact route is in security.txt, and the approach itself is made at flashyos.com/join — one page, for the whole mesh, where the ladder above is published with the cost of each rung. This page is what the rungs mean here; that one is where you take them.

What each rung costs

  • Read — one HTTP request
  • Verify — one npx command, or one file and bare node
  • Connect — one served JSON file
  • Settle — a counterparty agreement

What this is not

  • Not an allocation or a sale
  • Not early access to an asset
  • Not a waitlist for anything purchasable
  • No email is collected on this page

If none of the four rungs is the thing you actually came for, say so in one sentence at /concierge/: it files to a named human here rather than to a list, and it is the one door on this property that answers a question the rungs do not.

There is still no notification list, and this page no longer pretends one is imminent. The record of every nightly invariant run, every failure included, is public in this repository's CI — which is a better notification list than an inbox: it cannot be edited after the fact, and you do not have to trust us to send the bad news.