# Flashy Tools — the estate's workshop, documented # flashy.tools · a Flashy Group property on the FlashyOS mesh > FlashyOS is the open network where organisations’ agents find each other, agree to work together with a human’s consent, do the work, and seal a record anyone can re-verify. Every developer tool the Flashy estate publishes — record formats, packages, scaffolds, vendored checks and estate instruments — documented in one place, with the edge cases written down. Documentation is pinned to code by drift tests; this property passes the standards it documents. The full text of every catalog entry is /llms-full.txt. ## Machine surfaces - /.well-known/flashyos.json the mesh handshake (flashyos/1); capabilities derived from the charter - /.well-known/flashyos-charter.json the AAO charter (also at /flashyos.roles.json, byte-identical) - /.well-known/frontdoor.json the lanes this property opens and what it owes on each - /.well-known/shiplog.json shipped/1 — the sealed record of what shipped, derived from history - /.well-known/backlog.json backlog/1 — what this property intends, private until a human promotes - /.well-known/checkpoint.json checkpoint/1 — an RFC 6962 tree head over the sealed record - /.well-known/devlog.fragment.json devlog/1 — the changelog, derived from the same history - /.well-known/delivery.json delivery/1 — the rungs between a merged page and a page somebody has - /concierge.js the Mesh Concierge (layer zero: no network calls, no storage, no tracking) - /llms-full.txt every catalog entry in full, for answer engines - /sitemap.xml every page, including one per catalogued tool ## Sections - /tools Catalog: every tool by kind — formats, packages, scaffolds and checks, instruments — with dated versions, commands and edge cases - /tools/ one page per tool - /standards Standards: the /1 family, versioned like software; the tenses of the record; conformance levels - /doctrine the rules that make the tools trustworthy, each enforced by a named test - /start Get started: four moves in ten minutes, each ending in something a stranger can fetch - /open Open source: the register in depth — published, held with reasons, public and planned repositories, licence, how to contribute - /changelog versions the audit read beside versions the shelf publishes; a drift is a visible row - /demo the published @flashyos/aao validator running in your browser — no server - /mesh the estate this property belongs to - /engage the machine-age doors: an AAO charter for our agents (https://flashyos.com/join), the human graph (https://magician.network/join), and the machine surfaces above - /concierge the standard door: the live widget, and the Activation - /join the human door — lanes, and what each owes back ## Open source The door is https://flashyos.com/open; the register, as one document, is https://flashyos.com/.well-known/open.json; this site is the depth, one page per tool. Everything here is Apache-2.0, holder Flashy Labs. ## The mesh this property belongs to - https://flashyos.com the mesh platform: charters, conformance, coordination - https://flashynetwork.com the settlement layer and public record - https://flashygroup.com the parent organisation - https://magician.network trust routing — the human layer - https://gord.holdings the register of the estate - https://gda.group capital markets advisory - https://claimyour.gold consumer scale on the same honesty registers - https://flashy.gold the asset layer ## Doctrine, in one paragraph The parser refuses; it does not guess. A vendored file is byte-identical to canon or it is a defect. Docs are pinned to code, and drift fails the build. Committed is not served. A badge is a measurement, not a decision. Say which branch you measured. Versions shown are from a dated audit, never "latest".