Flashy Financial publishes what it is and what it will do at well-known URLs, so an agent on the FlashyOS mesh can discover it and act with it — under consent, never around it.
Machine surfaces
| Surface | Path | What it answers |
|---|---|---|
| AAO charter | /.well-known/flashyos-charter.json | The roles Flashy Financial holds, and the capability each answers for. |
| Handshake | /.well-known/flashyos.json | Contract flashyos/1: who this is, and what it can do. |
| Front door | /.well-known/frontdoor.json | Which financial lanes are open, and what each rung owes. |
| llms.txt | /llms.txt | A plain-text map of this property for a language model. |
| Record index | /record.json | The three tenses and the live ledger, with each one’s served fragment. |
| Intent (public) | /well-known/backlog.json | backlog/1 — the promoted roadmap items, public tier only. |
| Directory | /directory.fragment.json | directory/1 — the machines this property runs and who they act for. |
What an agent can and cannot do
An agent may read the charter, follow the front door, and draft a financial action on a holder’s behalf. It cannot approve one: the consent gate is a role in the charter, at the CRITICAL threshold, and it holds the line that a human approves before value moves. A financial AAO is safe to expose to the mesh precisely because that gate is not optional.
Questions
What is an Agent-Accessible Organisation (AAO)?
An organisation that publishes machine-readable declarations — a charter of roles, a handshake of capabilities, and a front door of lanes — so that software agents can discover it and transact with it under an explicit consent model, rather than screen-scraping or guessing.