UNDERSTAND
Glossary
The settlement vocabulary, defined once and emitted as DefinedTermSet. Each term has its own permalink and is cited from the pages that use it.
| Settlement | The point at which a movement of Flashy Gold becomes final and recorded. |
| Invariant | A condition that must hold after every write. Here: Σ(entries) = Σ(balances). |
| Minor unit | The smallest indivisible quantity of an asset. Flashy Gold has two decimal places. |
| Issuance | The creation of Flashy Gold against a funded source. Never discretionary. |
| Reconciliation | Proving two independently derived sums agree, at a stated instant. |
| Attestation | A third party stating that a reconciliation was performed. |
| Explorer | A public, read-only surface over a ledger. It cannot write and holds no keys. |
| Anchor | A cryptographic commitment to a snapshot, published to a public chain so the record for a given date cannot later be altered without detection. |
| Settlement rail | The append-only service of record that seals each settlement to a hash and issues inclusion and consistency proofs over them. flashy-rails runs it; this property reads its transparency log and verifies the proofs in the reader’s own browser. |
| Transparency log (RFC 6962) | An append-only Merkle log in the shape RFC 6962 defines for certificate transparency. Two things become checkable without trusting the operator: that a given entry is in the log (inclusion), and that the log only ever appended, never rewrote (consistency). |
| Checkpoint (tree head) | A single hash committing to every entry in a log at one instant — the root of the Merkle tree. A proof is checked against a published head, and a newer head is valid only if it is an append-only extension of an older one. |
| Issuer token (rewards:issue) | A short-lived credential carrying the rewards:issue scope, minted by FlashyID with its own OIDC key and verified by the settlement rail. It authorises one named issuer to write, and its public half is already in FlashyID’s JWKS, so nothing new has to be published. |
| Cross-organizational settlement and reputation layer | The layer that records what organizations’ agents actually finish together — each settlement sealed as canonical JSON plus its sha256 at the moment of resolution, never recomputed — and derives reputation only from that settled work, never from activity volume or proposals. This property is that layer for the AAO Stack: the record is public, and anyone can recompute the hashes (npx @flashyos/verify). Owner’s definition: AAO stack · Agentic Autonomous Organization |
| Agentic Autonomous Operating Stack | The AAO Stack: the infrastructure an economy of Agentic Autonomous Organizations runs on — coordination (FlashyOS), memory (Flashy Mind, in design), open settlement-ledger rules with Flashy Gold as first asset, agent identity (FlashyID), and an education layer (Flashy Academy). This property publishes the stack’s sealed settlement record; FlashyOS defines the stack and the category, and gda.group publishes the thesis. Owner’s definition: AAO stack · Agentic Autonomous Organization |
| Machine-readable mesh | A network whose organisations publish the facts about themselves — who they are, what they can do, who is accountable, and what they have completed — at fixed paths in fixed formats, readable without an integration, an account, or permission. An API is a machine-readable interface you request access to; this is machine-readable identity you did not have to ask for. This property is the fourth of those surfaces: the sealed record. Canonical definition: flashyos.com/concepts/machine-readable-mesh. |
| DeAI Operating System | The control layer for decentralized AI: identity, permissions, accountability and a verifiable record for autonomous agents. FlashyOS implements it; this property is the public settlement record it publishes to. Canonical definition: flashyos.com. |
This is the vocabulary nobody else in the group owns. The For-Gold economy is defined on flashygroup.com and the institutional reads live on gda.group; these terms are settlement engineering, and the other properties cite them here.