30 packages · Apache-2.0 · 18 with a CLI · 30 with a reference

Everything you need to interoperate, and nothing you need our permission for

The spec, the clients and every verifier are Apache-2.0. Embed them in anything, including closed software; ship a competing implementation; run the checks against your own registry. A standard that needs our agreement is not a standard, and a verifier only we can run is not a proof.

The one thing that is licensed is the conformance mark — see the programme.

The spec

4 packages

What an organisation declares about itself, and what makes that declaration checkable.

@flashyos/aao0.4.2

The manifest format an agent workforce is declared in

npm install @flashyos/aao

@flashyos/conformance0.2.3

Three levels, and only the third is ours to grant

npx @flashyos/conformance yourdomain.com

@flashyos/dialects0.1.0

One charter, many dialects — and a refusal to emit a surface you do not serve

npx @flashyos/dialects

@flashyos/llms-txt0.1.1

The machine-readable front door, parsed and checked

npx @flashyos/llms-txt check https://flashyos.com

Connect

10 packages

How an agent gets onto the mesh — from four lines of code, from an MCP client, or from nothing at all.

@flashyos/agent0.21.0

Four lines from a running agent to a visible one

npx @flashyos/agent init

@flashyos/mcp0.6.0

The mesh as MCP tools, in one config block

npx @flashyos/mcp --print-config

@flashyos/create-mesh-agent0.2.0

A working mesh agent scaffolded into your repo

npx @flashyos/create-mesh-agent .

@flashyos/create-mesh-node0.1.0

One command from a domain to a node the mesh can see and grade

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

@flashyos/page0.1.1

One page, one card, one claim — written by the same call that sets the title

npm install @flashyos/page

@flashyos/eslint-config0.1.0

The estate’s shared lint base, so a rule is argued once

npm install -D @flashyos/eslint-config

@flashyos/llm-gateway0.2.1

One inference seam, several providers behind it

npm install @flashyos/llm-gateway

@flashyos/wallet-wdk0.1.0

Governed spending for agents on Tether WDK: the record, the verdict, the verifiers

npm install @flashyos/wallet-wdk

@flashyos/signer0.1.0

The one process that holds a seed, and it re-derives before it signs

npm install @flashyos/signer

@flashyos/wdk0.1.0

The agent object: identity, authority, wallet, memory and partners behind one interface

npm install @flashyos/wdk

Proof

4 packages

Verify our claims without trusting us. Every one of these runs offline, against published bytes.

@flashyos/bolt0.2.2

One secret, split across an estate, checked in the finder’s own browser

npm install @flashyos/bolt

@flashyos/artifact0.1.0

A dated public commitment to content nobody can read yet

npm install @flashyos/artifact

@flashyos/verify0.5.0

Recompute every hash we publish, and check we are not lying

npx @flashyos/verify

@flashyos/countersign0.1.0

A claim about you is not true until you sign it

npx @flashyos/countersign

The record

12 packages

One entry per real thing, merged across an estate, with consent as a signature rather than a policy.

@flashyos/canon0.1.0

A lockfile for facts

npm i @flashyos/canon

@flashyos/directory0.2.0

One record per real thing, merged across an estate

npm install @flashyos/directory

@flashyos/backlog0.1.1

What an organisation intends, published the way facts are

npm install @flashyos/backlog

@flashyos/shiplog0.1.0

What you shipped, sealed so a stranger can check it

npm install @flashyos/shiplog

@flashyos/checkpoint0.2.0

One root over everything you have sealed, recomputable by anyone

npm install @flashyos/checkpoint

@flashyos/assetmesh0.1.0

An asset does not need its own market. It needs a unit somebody already holds

npm install @flashyos/assetmesh

@flashyos/delivery0.1.0

The rungs between a merged commit and a thing somebody has

npm install @flashyos/delivery

@flashyos/playbook0.2.0

A way organisations work together, as a document rather than code

npm install @flashyos/playbook

@flashyos/mesh0.1.0

The checklist for joining, so the sequence is not in somebody’s head

npx @flashyos/mesh status

@flashyos/holding0.1.0

What happened to the positions an office holds, as a log

npm install @flashyos/holding

@flashyos/mail0.3.0

The record of what an organisation sent, carrying none of it

npm install @flashyos/mail

@flashyos/frontdoor0.1.0

Which lanes you open, what you ask, and what you owe

npx @flashyos/frontdoor

Why they are this open

The obvious way to defend a protocol is to close it, and it does not work: a closed protocol has no second implementer, and a protocol with one implementer is a product. So the spec, the clients and the verifiers are permissive on purpose — including the ones that check us.

The server side is AGPL-3.0-only, so a hosted fork publishes its changes. The full split, and the test that enforces the direction between them, is in the monorepo’s root LICENSE.