Machine surfaces · 10 · served on all three domains
What a machine reads here
Ten surfaces, each at the path its own checker actually looks at. Publishing a file is not the same as serving it where it is read, and this estate has learned that three separate times.
| Surface | Profile | What it says |
|---|---|---|
| /.well-known/flashyos.json | flashyos/1 | The handshake. Who this organisation is, what it can do, whether each arm has earned its name, and where the network is joined. Not served yet. |
| /.well-known/flashyos-charter.json | AAO | The charter. Which functions this organisation performs, which roles perform them, and the impact threshold above which a human approves. Not served yet. |
| /.well-known/frontdoor.json | frontdoor/1 | The door. Which lanes are open, what each rung costs, and what this group owes you for climbing one. |
| /.well-known/backlog.json | backlog/1 | The future tense. What this group intends to do and what it wants from somebody else in order to do it. Public tier only. |
| /.well-known/shiplog.json | shipped/1 | The past tense. Every thing that shipped, sealed and never revised. Absent until this repository has a history of its own. |
| /.well-known/checkpoint.json | checkpoint/1 | An RFC 6962 tree head over the sealed claims above. It commits to nothing while the log is empty, and its size field says so. |
| /.well-known/delivery.json | delivery/1 | What actually reached somebody, measured rather than declared. The last four rungs are settled by a fetch, not by an assertion. |
| /directory.fragment.json | directory/0.1 | This group's fragment of the record: the organisation, its three domains and which arms are earned, the machines it runs, and the work it publishes. |
| /llms.txt | — | What this property is and every page it publishes, in the form a language model reads first. |
| /sitemap.xml | — | Every page, with the date each was last checked. |
How to check that we are telling the truth
Do not take the list above as evidence that a domain serves any of it. Run the estate's own published checker against each of the three, which is what catches the failure a repository cannot see:
| npx @flashyos/conformance h3alth.group --level 2 |
| npx @flashyos/conformance h3alth.ventures --level 2 |
| npx @flashyos/conformance h3alth.capital --level 2 |
All three, every time. A loop that writes one output and skips two is how a sibling stays broken while the parent looks fine.