OPEN SOURCE · THE WEB 4 STACK
The spec is open.
The network is a product.
Everything a stranger needs to check our claims or build against us ships in the open under Apache-2.0: the manifest format, the conformance suite, the SDK, the settlement verifier, the ledger rules. The services that run them live — the mesh, the books, the floor — are the product. That line is stated here once and holds everywhere.
npx @flashyos/verify
This page is a view of one document. /.well-known/open.json carries the same 30 published packages, the 16 held until a first adopter, and every repository with the visibility the register last read for it. Depth per tool, with the edge cases written down, is flashy.tools.
The Web 4 stack
The open formats above are rungs of a larger map. The agentic internet — the web of the Web 4 era GDA Group defines — is a stack of open protocols through which software agents discover, identify, authorize, trust, transact with and audit one another. Each layer answers one question, and each is a spec plus an implementation with its own repository. The whole map, re-measured per repo, is the Web 4 hub; the nine layers, rendered from the machine-readable web4/1 map this page reads rather than restates:
A repository is linked only when the register has read it as public; the rest are named and not linked, because a link a stranger cannot open is a claim. The machine twin is served at /.well-known/stack.json.
The wire formats
The standard is a handful of on-the-wire contracts, each with a version in its name and a normative home. All Apache-2.0 — fork them, ship a competing implementation, run the suite against your own register. What turns a prose spec into testable interop is a portable conformance suite: language-neutral vectors with expected verdicts, so a parser in any language can prove it accepts and rejects the same documents ours does. 7 of 16 ship one today; the rest say so rather than pretend. The register of every format, with its profile and schema, is /protocols.
The one file a stranger reads first — who you are, and where the rest of your record lives
An agent workforce declared the way a cap table declares ownership — who may do what, and who answers for it
One record per real thing, merged across an estate, with consent as a signature rather than a policy
A countersignature from the party a claim is about — checkable offline from two published keys, by anyone, forever
Which lanes you open to strangers, what you ask at each, and what you owe in return
One sealed entry per thing that shipped — dated, attributed, and checkable by a stranger
What an organisation intends, published the way facts are — and decaying, so it cannot lie by inertia
One RFC 6962 root over everything you have sealed, recomputable by anyone, holding no data itself
What an organisation sent — lane, disposition, counterparty domain, time — and nothing a message was about
What happened to the positions an office holds — transitions, never states, so a correction is an entry rather than an edit
How two organisations actually run a thing together — named roles, ordered steps, and the evidence each step owes
A playbook instance with every party’s human consent, sealed, and countersigned by every other party — a profile over formats that already exist, not a package
What one step of work leaves behind — actor, authority, input, tool, timestamp, output — sealed through the one canonicalisation and re-derivable offline
What an organisation handed over, to whom, and against which agreement
One word per property and a published commitment over the set — verified in the finder’s own browser, with no server behind it
Assets an organisation holds and the obligations it has issued against them, denominated in a unit that already circulates
Run any format's suite against your own parser: npx @flashyos/conformance yourdomain.com --level 2 grades a live domain; the per-format suites above check an implementation offline.
Packages · 30 published
One secret, split across an estate, checked in the finder’s own browser
A dated public commitment to content nobody can read yet
The manifest format an agent workforce is declared in
Four lines from a running agent to a visible one
The mesh as MCP tools, in one config block
A working mesh agent scaffolded into your repo
One command from a domain to a node the mesh can see and grade
Three levels, and only the third is ours to grant
Recompute every hash we publish, and check we are not lying
A lockfile for facts
A claim about you is not true until you sign it
One record per real thing, merged across an estate
What an organisation intends, published the way facts are
What you shipped, sealed so a stranger can check it
One root over everything you have sealed, recomputable by anyone
One page, one card, one claim — written by the same call that sets the title
An asset does not need its own market. It needs a unit somebody already holds
The rungs between a merged commit and a thing somebody has
A way organisations work together, as a document rather than code
The checklist for joining, so the sequence is not in somebody’s head
The estate’s shared lint base, so a rule is argued once
What happened to the positions an office holds, as a log
The record of what an organisation sent, carrying none of it
One charter, many dialects — and a refusal to emit a surface you do not serve
Which lanes you open, what you ask, and what you owe
The machine-readable front door, parsed and checked
One inference seam, several providers behind it
Governed spending for agents on Tether WDK: the record, the verdict, the verifiers
The one process that holds a seed, and it re-derives before it signs
The agent object: identity, authority, wallet, memory and partners behind one interface
Held · 16 until a first adopter
Apache-2.0 in the tree and deliberately off every registry. A format is published on its first adopter, never before: a package with no user outside this estate would be a promise about stability nobody has tested. Each one carries the reason it waits.
Repositories
agent-dns/1 — domain→organisation→agent resolution over one DNS TXT record, with a dependency-free reference resolver.
agent/1 — the /.well-known/agent discovery document: how a site exposes an authenticated, discoverable, payable machine interface.
agentfile — answer the accountability question about an organisation in ninety seconds.
graph/1 — the vendor-neutral spec for the universal graph of the agentic internet: who and what exists, and the evidenced relations between them.
pay-policy/1 — the vendor-neutral payment-policy abstraction for agents: an allow/deny/escalate evaluator, not a wallet.
Bastion — the gateway that exposes an existing site or API as a secure, authenticated, payable machine interface. In design.
@flashyos/conformance-kit — run a conformance corpus against any executable, in any language.
The documentation hub for the Flashy ecosystem.
Working examples and tutorials for the estate’s packages.
@flashylabs/ledger — the multi-asset ledger other properties post through.
delegation/1 — the vendor-neutral spec, schema, vectors and checker for cryptographically provable delegated authority for agents.
The public home of the estate’s accountability formats — aao/0.1, flashyos/1, directory/1, frontdoor/1 and the rest: spec, schema, conformance corpus and a dependency-free checker per format.
@flashyos/tools — small answers to questions that fail silently; the estate’s charter and provisioning tooling.
The public mirror of the WDK wallet stack: the extractor packs, the remote-authorization policy, the isolated signer and the agent object.
The canonical, vendor-neutral home of intent/1 — spec, JSON Schema, conformance vectors and a dependency-free checker.
@flashyos/mesh-lint — a GitHub Action for the checks that fail silently.
web4/1 — the machine-readable index of the Web 4 / agentic-internet stack: one document, a schema and a dependency-free checker.
Scan node_modules for installed @tetherto/wdk-* packages and report the chains each declares, refusing to guess at one it does not recognise.
A spending-policy layer for WDK wallets: grade a transfer against a per-agent envelope and return ALLOW, ESCALATE or DENY, with a reason.
A reference staking primitive for WDK wallets: lock a balance for a fixed term at a published rate; only yield is a real write, on close.
The human front door to the Web 4 stack: the map, the architecture, the principles and the rule for how a new protocol joins.
21 of 39 open-licensed repositories have been read as public. The others are named in the register and not linked here until a reading says a stranger can open them.
Planned, with their status
agentfile — answer the accountability question about an organisation in ninety seconds.
Not released. The formats it writes are published and stable; the seven questions and the writer are the work that remains. Nothing here is installable yet.
@flashyos/conformance-kit — run a conformance corpus against any executable, in any language.
Pre-1.0. The line protocol is the part worth freezing and it is deliberately tiny: `{id, set, input, context?}` in, `{id, valid, codes?}` out. It will be locked at 1.0 and has not changed since it was written.
The public home of the estate’s accountability formats — aao/0.1, flashyos/1, directory/1, frontdoor/1 and the rest: spec, schema, conformance corpus and a dependency-free checker per format.
The specifications are not here yet. They are Apache-2.0 today; carrying the packages out of the monorepo they were written in, *with their real commit history*, is a deliberate operation rather than a copy — a chain of title that begins on the day somebody remembered to copy the files is not a chain of title. Until that runs, this repository is the licence, the security policy and the direction.
@flashyos/tools — small answers to questions that fail silently; the estate’s charter and provisioning tooling.
Pre-1.0. `served` and `reachability` have been running against a thirty-eight repository estate for months; the API is small and unlikely to move, but the version says 0.x until somebody outside that estate has depended on it.
@flashyos/mesh-lint — a GitHub Action for the checks that fail silently.
Not released. The code is here; the distribution is not. The three checks run, are tested against fixtures rather than against the estate that found them, and `action.yml` is a composite action with no build step. What does not exist yet is a published package or a tag — measured 2026-09-23, `@flashyos/mesh-lint` answers 404 on npm and this repository has no tags — so `npx @flashyos/mesh-lint` and `uses: flashylabs/mesh-lint@v1` both fail today. Clone it and run `node src/cli.mjs` until they do. That gap is named here rather than left for the first person who copies a line out of the section above, which is the same defect this package's own `well-known` check exists to find.
Also open
The brand & press kit (marks, lockups, tokens, usage rules — downloadable). The spec page for the format itself lives at /aao, and the naming standard at /standard. Together these packages are the open half of an agent execution protocol; the network that enforces it live is the execution infrastructure.
Every repo we open carries a sealed ⚡ STRIKE — a sha256 commitment whose preimage a finder can hand us, written in that repo's STRIKERS.md. The count is measured at the graph, never typed here.
