INTEGRATE
Machine surfaces
Generated from the same registry module that renders the pages, so a machine and a person cannot be told different things.
| Surface | What it carries |
|---|---|
| /llms.txt | This property, in the form a language model reads |
| /network.json | The record state and every published figure, as data |
| /group.json | Where this property sits in the group, in the shape every sibling publishes |
| /sitemap.xml | Every route, with its change frequency |
| /.well-known/security.txt | RFC 9116. One disclosure address, with an expiry computed when it is served |
| /.well-known/flashyos.json | The mesh handshake (flashyos/1): which org this is, and where the network is joined |
| /.well-known/flashyos-charter.json | The AAO charter (aao 0.1): the standing roles this org holds, and which human answers for them |
| /.well-known/checkpoint.json | checkpoint/1: a Merkle root over this property’s sealed record, recomputable from the fragments |
| /.well-known/tally.json | tally/1: every figure the estate measures about itself, each declaring who has to act for it to move |
| /.well-known/notary-log.json | notary/1: the estate’s append-only transparency log — the leaf stream, so the head and every proof rebuild independently |
| /.well-known/settlement.fragment.json | notary/1 source: one settlement/1 leaf per public ledger entry — this property’s own economy, hashed live, folded into the log |
| /.well-known/devlog.fragment.json | devlog/1: this property’s human-readable changelog, derived from commit history — the public record every devlog/1 leaf on the notary log hashes |
| /.well-known/notary-sources.json | The fan-in’s source register: every log this property fetches and folds — read it back to confirm a registration landed |
| /.well-known/notary-sources.schema.json | The JSON Schema a source registration is checked against, so the shape of a submission is pinned and self-serve |
| /.well-known/pinned.json | pinned/1: this property’s drift declaration — every vendored copy it holds, the flashyos source it derives from, and the revision it is current against, so a watcher flags a stale copy without cloning anything |
| Dataset JSON-LD | On every entry permalink, so an entry is citable at entry level |
| DefinedTermSet | On /glossary/, so the settlement vocabulary is machine-readable |
These are linked visibly in the footer rather than buried, which is the rule for this property. The registry module is the single source: if a route exists, it is in the nav, the footer, the sitemap and llms.txt, with the same status glyph in all four.