The catalog
Tools of the estate
Versions are measured, never typed: each one was read from a checkout of the package on 2026-10-30 and says so. A package with no checkout to read shows as unverified rather than as a number somebody remembered — and never as “latest”. Each row carries the brand that publishes it as a badge; the grouping below stays by layer and by kind, because who answers for a tool is a fact about the row, not a shelf to sort it onto. The same catalog is served as data at /.well-known/tools.json.
By Web 4 stack layer
The tools that answer a layer of the agentic-internet stack, in the map’s order. A tool that answers no stack question — an estate instrument, a vendored check — appears only under its kind below.
Identity
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashylabs/flashyid-specFlashyOS | delegation/1 — the Identity layer’s contract for a cryptographically provable chain of attenuated authority that runs human → organisation → agent → sub-agent → session and can never grow on the way down. The spec, a JSON Schema, vectors and a dependency-free checker. | 0.1.0 |
Graph
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashylabs/agentgraphFlashyOS | graph/1 — the Graph layer’s answer to “what exists?”: people, organisations, agents, capabilities, tools and assets as nodes and the evidenced relationships between them as edges, and deliberately nothing about how good, how much, or how trusted. It extends therealm’s realm/1 registry rather than reinventing it. | 0.1.0 |
| realm/1Sibling project | realm/1 — the Graph layer’s registry: the agent-navigable world above the estate’s houses, where one fetch of /.well-known/realm.json gets a machine every house, its machine door and the Chronicle feed. graph/1 derives its org/ nodes from this manifest; the human side enters through a house and an archetype folded from the same register. | unverified |
Discovery
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashylabs/intent-specFlashyOS | intent/1 — the Discovery layer’s future tense: one JSON document per repository saying what an organisation intends to do next, served at its own /.well-known/intent.json and merged by anyone. The spec, its schema, the conformance vectors and a dependency-free checker. | 0.0.0 |
Trust
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| trust/1 + introduction/1Sibling project | trust/1 and introduction/1 — the Trust layer’s engine: trust/1 edges each carrying a register (measured, asserted or estimated) and no expiry field, and sealed introduction/1 outcomes, routed through a consent machine with a veil. The reference implementation is @magician-network/core; the machine-readable schemas live in magician/schemas. | unverified |
| rites-protocolSibling project | ritual/1 — the Trust layer’s present tense: the recurring, witnessed, consequence-bearing act between backlog/1 (the future) and shipped/1 (the past). Liturgies and the observances performed against them, climbing a performed → witnessed → consecrated ladder by transition, never by assertion. | unverified |
Gateway
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashylabs/agent-wellknownFlashyOS | agent/1 — the Gateway layer’s discovery document at /.well-known/agent: one file through which a website tells an agent who is accountable, which actions it may take, where each lives, what each costs in whole minor units, and how to pay and authenticate. The open half — the spec, schema, checker and vectors. | 0.0.0 |
| @flashylabs/agent-dnsFlashyOS | agent-dns/1 — the Gateway layer’s naming step: one DNS TXT record at _agent.<domain> pointing at the domain’s agent/1 document, so a machine gets from a domain name to an organisation’s agents without asking a directory first. DNS points; the document describes. | 0.1.0 |
| @flashylabs/bastionFlashyOS | Bastion — a commercial gateway that puts a secure, authenticated, discoverable, payable machine interface in front of an existing website or API: /.well-known/agent derived from config, callers authenticated by delegation/1 chains, calls gated by pay-policy/1, a receipt per action. The revenue layer over the open Gateway specs, not a protocol. | 0.0.0 |
Commerce
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashylabs/agentpayFlashyOS | pay-policy/1 — the Commerce layer’s policy format and a pure allow/deny/escalate evaluator for agents that spend, over any rail: given a policy, a proposed payment and the period’s spent-so-far, may it go, must it stop, or must a person decide. Not a wallet; the rails and the signing live elsewhere. | 0.1.0 |
| @flashy/sdkFlashyOS | @flashy/sdk — a zero-dependency, type-safe client for ClaimYour.Gold’s Hunter Identity API: report engagement (create a skill event) and read a public hunter record, from other systems. Every engagement requires an idempotency key and the server, never the caller, prices the activity. | unverified |
Audit
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| chronicle/1Sibling project | chronicle/1 — the Audit layer’s first worked instance: agent-drafted news where every factual claim carries a receipt (the real sealed record it rests on, where it is served, and the digest to check it against). A claim with no citation cannot validate; verification is computed against the cited records, never asserted. | unverified |
Spanning
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| stack.jsonFlashyOS | web4/1 — the machine-readable index of the whole Web 4 stack: every layer, the question it answers, the repositories that implement it and their contract, status and visibility, as one document served at /.well-known/stack.json. The map an agent reads; the human twin is the web4 hub. This property carries a byte copy at src/data/stack.json. | 0.1.0 |
Teaching
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| web4 (the hub)FlashyOS | The Web 4 hub — the human front door to the stack: the map, the architecture, the principles, and the rule for how a new protocol joins, holding no protocol code. The machine-readable twin is stack.json (web4/1); this renders the human table and never duplicates that file’s data. | 0.1.0 |
| flashy-docsFlashyOS | Flashy Docs — the documentation hub for the four core systems (Ledger, Rails, Magician, FlashyID): architecture, concept guides and an API reference measured against a named commit of each package’s source. Explanations live here; the runnable code lives in flashy-examples. | 1.0.0 |
| flashy-examplesFlashyOS | Flashy Examples — fourteen runnable, tested examples for the estate’s packages and standards: append-only settlement, consent-gated transfer, sealed introductions, attenuation-only delegation, and the intent/1, ritual/1 and aao/0.1 formats, each teaching one invariant with its refusals. | 1.0.0 |
By kind
Record formats
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashyos/aaoFlashyOS | The AAO charter standard: named roles, a human accountable by email, and approval thresholds an agent cannot cross alone. The manifest spec, its JSON Schema, and the validators every checker in the estate imports. | 0.4.2 |
| @flashyos/directoryFlashyOS | directory/1 — the estate’s record: one entity per real thing, emitted as federated fragments by each repository, merged with one authority per id. The vocabulary (KINDS, EDGE_TYPES, EDGE_REQUIRES), the merge, and the validator. | 0.2.0 |
| @flashyos/shiplogFlashyOS | shipped/1 — the past tense of a record. One sealed entry per thing that shipped, derived from first-parent commit history, emitted per repository, never edited after sealing. | 0.1.0 |
| @flashyos/backlogFlashyOS | backlog/1 — the future tense. One item per intention, filed where the work happens, decaying unless renewed, private until a named human promotes it. | 0.1.1 |
| @flashyos/checkpointFlashyOS | checkpoint/1 — an RFC 6962 Merkle tree head over the sealed claims a property publishes. A static file beside the fragments: no server, no collector, no uptime. | 0.2.0 |
| @flashyos/countersignFlashyOS | Proof over the record: countersignature, delegation, audit, badge. The layer that lets the party a claim is about sign the claim. | 0.1.0 |
| @flashyos/frontdoorFlashyOS | frontdoor/1 — a published door: which lanes an organisation opens, what it asks at each, and what it owes back — including the honest no-SLA rung. | 0.1.0 |
| @flashyos/holdingFlashyOS | holding/1 — what happened to the positions an office holds. Transitions, not states: current state is derived from an append-only log, never asserted. | 0.1.0 |
| @flashyos/deliveryFlashyOS | delivery/1 — the rungs between a merged commit and a thing somebody actually has. Publishes where on that ladder each shipped thing stands. | 0.1.0 |
| @flashyos/canonFlashyOS | canon/1 — a lockfile for facts. One authority per fact, fetched by every property that renders it, so a number is written once and cannot drift between pages. | 0.1.0 |
| @flashyos/playbookFlashyOS | playbook/1 — a way two or more organisations work together, as a published document rather than tribal memory. | 0.2.0 |
| @flashyos/boltFlashyOS | bolt/1 — one secret split across an estate: a hunt verified by sha256 commitment, in the finder’s own browser, with no server to trust. | 0.2.2 |
| @flashyos/mailFlashyOS | mail/1 and the estate’s mail control plane: a lane policy that refuses, a capture that demands a consent basis, a content-free event record, and a transport seam so the provider is a variable. | 0.3.0 |
| @flashyos/artifactFlashyOS | artifact/1: a dated public commitment to content nobody can read yet. Existence precedes discovery. | 0.1.0 |
| @flashyos/assetmeshFlashyOS | rwa/1: a machine-readable record of a real-world asset, the attestations that stand behind it, and the obligations issued against it. Dependency-free, published at your own domain, verifiable by anyone. | 0.1.0 |
| @flashylabs/intent-specFlashyOS | intent/1 — the Discovery layer’s future tense: one JSON document per repository saying what an organisation intends to do next, served at its own /.well-known/intent.json and merged by anyone. The spec, its schema, the conformance vectors and a dependency-free checker. | 0.0.0 |
| @flashylabs/flashyid-specFlashyOS | delegation/1 — the Identity layer’s contract for a cryptographically provable chain of attenuated authority that runs human → organisation → agent → sub-agent → session and can never grow on the way down. The spec, a JSON Schema, vectors and a dependency-free checker. | 0.1.0 |
| @flashylabs/agent-wellknownFlashyOS | agent/1 — the Gateway layer’s discovery document at /.well-known/agent: one file through which a website tells an agent who is accountable, which actions it may take, where each lives, what each costs in whole minor units, and how to pay and authenticate. The open half — the spec, schema, checker and vectors. | 0.0.0 |
| @flashylabs/agent-dnsFlashyOS | agent-dns/1 — the Gateway layer’s naming step: one DNS TXT record at _agent.<domain> pointing at the domain’s agent/1 document, so a machine gets from a domain name to an organisation’s agents without asking a directory first. DNS points; the document describes. | 0.1.0 |
| @flashylabs/agentgraphFlashyOS | graph/1 — the Graph layer’s answer to “what exists?”: people, organisations, agents, capabilities, tools and assets as nodes and the evidenced relationships between them as edges, and deliberately nothing about how good, how much, or how trusted. It extends therealm’s realm/1 registry rather than reinventing it. | 0.1.0 |
| @flashylabs/agentpayFlashyOS | pay-policy/1 — the Commerce layer’s policy format and a pure allow/deny/escalate evaluator for agents that spend, over any rail: given a policy, a proposed payment and the period’s spent-so-far, may it go, must it stop, or must a person decide. Not a wallet; the rails and the signing live elsewhere. | 0.1.0 |
| stack.jsonFlashyOS | web4/1 — the machine-readable index of the whole Web 4 stack: every layer, the question it answers, the repositories that implement it and their contract, status and visibility, as one document served at /.well-known/stack.json. The map an agent reads; the human twin is the web4 hub. This property carries a byte copy at src/data/stack.json. | 0.1.0 |
| trust/1 + introduction/1Sibling project | trust/1 and introduction/1 — the Trust layer’s engine: trust/1 edges each carrying a register (measured, asserted or estimated) and no expiry field, and sealed introduction/1 outcomes, routed through a consent machine with a veil. The reference implementation is @magician-network/core; the machine-readable schemas live in magician/schemas. | unverified |
| rites-protocolSibling project | ritual/1 — the Trust layer’s present tense: the recurring, witnessed, consequence-bearing act between backlog/1 (the future) and shipped/1 (the past). Liturgies and the observances performed against them, climbing a performed → witnessed → consecrated ladder by transition, never by assertion. | unverified |
| chronicle/1Sibling project | chronicle/1 — the Audit layer’s first worked instance: agent-drafted news where every factual claim carries a receipt (the real sealed record it rests on, where it is served, and the digest to check it against). A claim with no citation cannot validate; verification is computed against the cited records, never asserted. | unverified |
| realm/1Sibling project | realm/1 — the Graph layer’s registry: the agent-navigable world above the estate’s houses, where one fetch of /.well-known/realm.json gets a machine every house, its machine door and the Chronicle feed. graph/1 derives its org/ nodes from this manifest; the human side enters through a house and an archetype folded from the same register. | unverified |
Packages
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashyos/verifyFlashyOS | Open, offline verification of settlements, receipts and handshakes: fetch the public feed, recompute every digest, trust nothing. | 0.5.0 |
| @flashyos/llms-txtFlashyOS | Parse, validate and build llms.txt files — the machine door every estate property serves beside its human one. | 0.1.1 |
| @flashyos/conformanceFlashyOS | Run the conformance suite against any live domain, audit a charter+handshake pair in-process (auditProperty / assertProperty), or scaffold a new property (init). | 0.2.3 |
| @flashyos/agentFlashyOS | The SDK agents import to report state to the mesh: heartbeat, work claims, and the consent-gated write paths. | 0.21.0 |
| @flashyos/mcpFlashyOS | The same mesh surface as the SDK, exposed as Model Context Protocol tools — connect any MCP-speaking agent to the mesh in one config block. | 0.6.0 |
| @flashyos/llm-gatewayFlashyOS | Provider-agnostic inference seam: adapters, automatic failover, metering ceilings, and an empty-success guard. | 0.2.1 |
| @flashyos/animoca-mindsFlashyOS | A typed client for Animoca’s Minds Builder API and Minds Connect, importing none of their code: the nine Builder API calls and the three Minds Connect OAuth 2.1 PKCE endpoints as typed functions over one injectable transport, with a recorded fixture to test against and a refusal that carries a status code and never a response body. | unverified |
| @flashyos/ledgerFlashyOS | Append-only, multi-asset settlement ledger. Storage-agnostic by construction; integer amounts; hash-chain verifiable. | 1.0.1 |
| @flashylabs/railsFlashyOS | The settlement and authorisation layer of Flashy Finance: a thin service over @flashyos/ledger that holds Flashy Gold, issues rule-bound rewards, enforces the draft → execute consent gate, and honours attenuated flashyID grants. | 1.0.0 |
| @flashyid/sdkFlashyID | The relying-party surface for Flashy ID delegated authority: verify an assertion is genuinely from Flashy ID and that the delegation it carries authorises a specific action, from one import, holding no secret. Plus the grant kernel (issue / attenuate / verify / permits) and the rail token minters. | 0.2.0 |
| @flashyfinancial/wdk-policy-guardFlashyFinancial | A spending-policy layer for wallets built on Tether’s WDK, or any wallet SDK. Grades a proposed spend against a per-agent envelope — chain, kind, asset and destination allowlists, a per-transaction cap, a daily cap — before anything signs, and returns ALLOW, ESCALATE, or DENY, always with a reason. | 0.3.0 |
| @flashyfinancial/wdk-staking-kitFlashyFinancial | A reference staking primitive for wallets built on Tether’s WDK. Locks a balance into a fixed-term tier at a published rate, with no on-chain contract required: a lock earmarks a balance a provider already credits, and only the yield, paid on close, is a real write. | 0.3.0 |
| @flashyfinancial/wdk-capability-auditFlashyFinancial | A capability audit for wallets built on Tether’s WDK: scans a project’s node_modules for every installed @tetherto/wdk-* package, reads what each declares about the chains it supports, and classifies each chain as mainnet, testnet or unknown — against a small hand-maintained registry, never a guess. | 0.2.0 |
| @flashyos/wallet-wdkFlashyOS | Governed economic agency for FlashyOS agents on Tether WDK: the AAO WalletCapability, a FlashyOS authorizer client, an MCP elicitation handler, and a WDK policy rule that defers to the authorization plane. | 0.1.0 |
| @flashyos/signerFlashyOS | The isolated signer for the FlashyOS wallet authorization plane: verifies an Ed25519-signed SpendAuthorization, re-derives the operation from the real call, refuses on any mismatch, executes through Tether WDK, and reports settlement. Holds the seed; never holds the plane’s private key. | 0.1.0 |
| @flashyos/wdkFlashyOS | The FlashyOS agent object: identity, authority, wallet, memory and partners behind one interface. Create an agent, give it an identity, provision financial capabilities on Tether WDK, set its permissions, let it transact, record what it did, coordinate it with other agents — through one object, one event system, any chain WDK reaches. | 0.1.0 |
| @flashyfinancial/wallet-wdkFlashyFinancial | The FlashyFinancial-scoped home of the wallet capability: the AAO WalletCapability, a FlashyOS authorizer client, an MCP elicitation handler, and a WDK policy rule that defers to the authorization plane — extracted verbatim from flashyos/packages/wallet-wdk into wallet-core. | 0.1.0 |
| @flashyfinancial/signerFlashyFinancial | The FlashyFinancial-scoped home of the isolated signer: verifies an Ed25519-signed SpendAuthorization, re-derives the operation from the real call, refuses on any mismatch, executes through Tether WDK, and reports settlement — extracted verbatim from flashyos/packages/signer into wallet-core. | 0.1.0 |
| @flashyfinancial/wdkFlashyFinancial | The FlashyFinancial-scoped home of the FlashyOS agent object: identity, authority, wallet, memory and partners behind one interface, on any chain Tether WDK reaches — extracted verbatim from flashyos/packages/wdk into wallet-core. | 0.1.0 |
| @flashyos/shiposFlashyOS | The release function, chartered: a consequence-ranked merge queue for every repository, plus the operator lane — the ranked list of actions only the accountable human can take. | 0.1.0 |
| @magician-network/coreSibling project | The trust-routing engine: trust/1 edges, the router with the veil, the consent machine, sealed introduction/1 outcomes, beacon/1 federation, grant/1, and the transport envelopes. | unverified |
| @magician-network/conciergeSibling project | The Mesh Concierge: one dependency-free script that puts the estate’s intent door on any site, filing to a named human at that property. The Activation standard and its pre-install check travel with it. | unverified |
| @flashyos/dialectsFlashyOS | One charter, many dialects: renders an organisation’s AAO charter into the surfaces other standards define — agents.txt, agents.json, an A2A Agent Card — so the same facts cannot drift between them. | 0.1.0 |
| @flashyos/meshFlashyOS | One checklist for joining the mesh: what a repository has adopted, what is left, and the exact command for each. | 0.1.0 |
| @flashyos/pageFlashyOS | One page, one card, one claim: per-page social images, canonical metadata and structured data for a property that expects to be cited by search engines and answered from by generative ones. | 0.1.1 |
| @flashylabs/bastionFlashyOS | Bastion — a commercial gateway that puts a secure, authenticated, discoverable, payable machine interface in front of an existing website or API: /.well-known/agent derived from config, callers authenticated by delegation/1 chains, calls gated by pay-policy/1, a receipt per action. The revenue layer over the open Gateway specs, not a protocol. | 0.0.0 |
| @flashy/sdkFlashyOS | @flashy/sdk — a zero-dependency, type-safe client for ClaimYour.Gold’s Hunter Identity API: report engagement (create a skill event) and read a public hunter record, from other systems. Every engagement requires an idempotency key and the server, never the caller, prices the activity. | unverified |
Scaffolds
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashyos/create-mesh-nodeFlashyOS | The one-command on-ramp: writes a charter, handshake, directory fragment and workflow, then verifies L2. | 0.1.0 |
| @flashyos/create-mesh-agentFlashyOS | Scaffold a dependency-free mesh starter agent into your repo — heartbeat, open-job polling, consent-gated actions. | 0.2.0 |
Vendored checks
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| The vendor-* familyFlashyOS | Eight dependency-free scripts every estate repository carries: check-charter, check-directory, check-frontdoor, vendor-shiplog, vendor-backlog, vendor-directory, vendor-checkpoint, vendor-check-activation. They run before an install, in repositories with no node_modules and sometimes no package.json. | — |
Estate instruments
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| estate-graphFlashyOS | Measures what the one-graph thesis is actually about: entities, relations, provenance, freshness, and the share of edges that cross a property boundary — with a ratio floor that fails regressions. | — |
| estate-hygieneFlashyOS | Thirteen checks across every repository, with the repositories missing each one named rather than counted, and a per-dimension ratchet floor — because a mean lets one dimension collapse behind another’s improvement. | — |
| estate-deployedFlashyOS | Fetches a domain’s served bytes and finds the commit whose committed copy is byte-identical — pinning exactly which commit a deploy serves, without trusting a date stamp or a CDN header. | — |
| estate-joinFlashyOS | Fetches every estate domain and asks both questions a stranger’s arrival poses: does the handshake carry join (the machine door), and does the page link it (the human door)? | — |
| estate-coherenceFlashyOS | The agreement check: of everything the estate publishes, how much is asserted by two properties from their own sides, with their own bases — the record’s only way to catch its own errors. | — |
| estate-countersignedFlashyOS | Counts the claims the estate makes about organisations that are not the estate, and how many those organisations have signed — the one number nobody here can raise. | — |
| The three registersFlashyOS | What each repository is licensed as, who did the work, and which standards each adopts — declared once, cross-checked against each other, surveyed against reality. | — |
| reachabilityFlashyOS | One rule about silence: classifies a failed fetch as unreachable, ambiguous, or refused — and every tool that makes a network call imports it, enforced by test. | — |
| workspace-depsFlashyOS | Finds internal semver ranges a version bump has silently outgrown — the failure that is green on a laptop and red only on a clean CI checkout. | — |
| route-livenessFlashyOS | A badge is a measurement, not a decision: LIVE is granted by a URL answering over the network, the way a stranger would reach it — never typed by hand. | — |
Shared configs
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| @flashyos/eslint-configFlashyOS | The estate’s shared lint base. Extending it costs three lines, which is why it exists: nine properties never adopted a linter while adoption meant writing a flat config from scratch. | 0.1.0 |
Teaching resources
| Tool | What it is | Version (measured 2026-10-30) |
|---|---|---|
| web4 (the hub)FlashyOS | The Web 4 hub — the human front door to the stack: the map, the architecture, the principles, and the rule for how a new protocol joins, holding no protocol code. The machine-readable twin is stack.json (web4/1); this renders the human table and never duplicates that file’s data. | 0.1.0 |
| flashy-docsFlashyOS | Flashy Docs — the documentation hub for the four core systems (Ledger, Rails, Magician, FlashyID): architecture, concept guides and an API reference measured against a named commit of each package’s source. Explanations live here; the runnable code lives in flashy-examples. | 1.0.0 |
| flashy-examplesFlashyOS | Flashy Examples — fourteen runnable, tested examples for the estate’s packages and standards: append-only settlement, consent-gated transfer, sealed introductions, attenuation-only delegation, and the intent/1, ritual/1 and aao/0.1 formats, each teaching one invariant with its refusals. | 1.0.0 |