The formats this estate publishes

Who an organisation is, federated across the properties that know it.

Proof over the record: countersignature, delegation, audit.

The past tense. One sealed entry per thing that shipped.

The future tense. One item per intention, and it decays.

An RFC 6962 tree head over the sealed claims a property publishes.

The estate-wide transparency log the sealed claims fold into.

What a group owns, who holds it, and under what licence.

Published on the first adopter, the rule reward/1 and ritual/1 already follow. A register nobody outside has adopted is a page about ourselves.

A universal graph of organisations, agents and the relations between them.

Agent-drafted news whose every claim carries a receipt against a sealed record.

The manifest that says what an organisation does and who answers for it.

The handshake an arriving agent reads first.

Which lanes an organisation opens, and what it owes on each.

One term, one authority. A citation is a link, never a copy.

That a verification of some assurance happened, and nothing about who.

Attenuated authority: a grant carries only a subset of the granter’s scopes, never more.

The machine-readable door an organisation serves at a well-known path.

The same-domain rule: an agent’s surfaces answer on the organisation’s own domain.

The nine-layer map of the agentic internet the AAO Stack sits on.

A machine-navigable index of the estate’s houses, their doors and their feeds.

What an organisation wants, in a form another organisation can match.

Relationship strength with a register on every figure.

A consent-gated introduction, sealed at its outcome.

What the fetch found: a machine surface read the way a stranger reads it.

How a repeatable piece of work runs, and what it owes at each step.

A playbook instance every party’s human has consented to, sealed and countersigned by every other party. A profile, not a package.

A versioned definition of ordered steps — agent, human approval, deterministic service — and an append-only run whose state is derived, never stored.

Published on the first adopter. No organisation outside this repository runs a workflow through it yet; the invoice-to-payment scenario in its own tests is the only adopter.

Real-world assets, with the obligations that travel with them.

What happened to a position. Transitions, never states.

One holding across books that are not one book.

Published on the first adopter. Flashy Financial is not operational, and a wallet format with no venue is a claim nothing can settle.

An accrual log for entitlements nothing can pay yet.

Deliberately accrues and pays nothing. It is published when there is a venue to settle into, and not before.

The rules under which an agent may spend — capped, purposed and revocable.

An agent’s standing per capability — a figure derived from verified history and never asserted (not trust/1: that identifier is Magician’s). Inputs and function published; the figure private and promote-only; its only power is to propose a change a person resolves.

Published on the first adopter, and not before the visibility rule for the figure has one: publishing the function invites publishing the number.

A signed verdict from an independent process that re-derives, refuses, holds or escalates a consequential action, with its own key and no import from what it guards.

Published with the first guardian deployed by a party other than the one it guards. Independence is the property, and no second deployment exists yet.

A content-free record of what an organisation sent, and on whose authority.

The present tense. Recurring, witnessed observances.

A world is a document: seven operations, laws that are data, and a proof that is the sequence of moves rather than a claim about it.

Published on the first adopter, the rule reward/1 and ritual/1 already follow. One world exists and it is ours, so a registry listing would be adoption theatre — it publishes the day somebody else writes a ruleset, which is the day the vocabulary stops being ours and starts being worth agreeing on.

Condition over time, so a reader can ask whether this was better last week.

Published on the first adopter outside this estate, the rule reward/1 and ritual/1 already follow.

The figures, and a refusal to publish only the flattering ones.

Published on the first adopter. A figures format adopted by nobody is a page about ourselves.

What is serving where, measured rather than declared.

Published on the first adopter. Deploy state is the estate’s own bookkeeping until somebody outside has a deploy to describe.

What each initiative spent on inference — token counts and request ids, never money; the cost is derived at read.

Emitted and read inside the estate today (the ops console serves a fragment, flashynetwork renders it), but the package is held private until an outside adopter installs it, the rule reward/1 and pulse/1 already follow.

Drift detection for derived content: a course, doc or figure declares {source, revision}, and a checker returns current / stale / unverifiable — the verdict derived, never stored.

Adopted inside the estate today by vendored copy (flashy.academy’s content-graph gate consumes it; flashyos pins its own docs through tools/pinned.mjs), the way every record format here travels. Held private until an outside adopter installs it, the rule reward/1 and pulse/1 already follow.

How a property is meant to sound, stated once: a person writes the register — banned phrases and a length band — and a shared linter checks a piece of copy against it before it ships. A convention, not a sealed format: nothing here is observed or witnessed.

The rule lived three times — once executable, twice as prose in a CLAUDE.md — before it was one package. Held private until an outside adopter installs it, the rule reward/1 and pulse/1 already follow; inside the estate it travels by vendored copy like every record format here.

The estate ring a property’s footer renders: every property, its group and whether it is live, read from the served feed with the four findings and null-never-zero.

A vendorable reader other properties copy, not yet on a registry; it publishes at the first property that vendors it rather than installs it.