Adoption
The ladder,
with its denominators
A format's own site is the worst place in the world to be loose about how many people use it. The tempting number is "observances performed" — and performing observances is entirely within our power, so it measures a cron job running rather than a practice happening.
Somebody else has to act
2 figures here move only when somebody outside acts, and every one of them reads zero. That is the honest state, not a gap in the record.
| Figure | Reading | Measured by |
|---|---|---|
| Organisations outside this estate publishing any of these formatsCaptive adoption — a client, a portfolio company, a shareholder’s business — is recorded separately and never added here. A company whose investor asks it to publish a file publishes the file; that is a fact about the relationship. | 0since 2026-08-01 | adoption-signal.json |
| Observances a second party has witnessedUnwitnessed practice moves nothing. The workflow that performs an observance can never witness it. | 0 of 6 | tools/estate-ritual.mjs |
We move these ourselves
Worth measuring, worth failing a build over, and worth nobody’s trust on its own. Every one ships with its denominator; a count ships with the date it counts from.
| Figure | Reading | Measured by |
|---|---|---|
| Observances a person has consecratedA consecration names a person, and the person is ours. Consecrating our own practice is not evidence about the practice — it sits here for that reason, beside the witness count that does not. | 0 of 6 | tools/estate-ritual.mjs |
| Observances performed across the estateAn observance is performed by an agent on a rhythm. Performing more of them is entirely within our power, which is why it sits on this side and why the rung below is the one that means anything. | 6since 2026-09-03 | tools/estate-ritual.mjs |
| Ritual — repositories holding it | 2 of 42 | tools/estate-standards.mjs |
The seal
Each figure carries a sha256 over its own canonical form; the document carries one over the ordered list of those and over every retirement, so the commitment covers what is no longer reported as well as what is. Sort every key at every level, keep array order, hash as UTF-8, and you get the same string.
- As at
- 2026-09-08
- Subject
- org/flashyos
- Digest
8eb4c756b304e751086279cd09d8ed280defa4f6621be9f8c3ff525571d33ec4
On the estate transparency log
Each observance is projected onto one content-free notary/1 leaf
and folded into flashynetwork.com's one
transparency log (source rites-ritual). Click a hash to land on that exact
leaf — its inclusion proof, recomputed in your own browser against the current tree
head. A leaf is a hash, a kind, a time and a ref; never who performed the observance, or what it
was.
0x2d40393adfe8785e…— ritual/1, 2026-09-28
How this page is kept honest
It renders adoption.json, a
tally/1 document measured from every repository's default branch and sealed. The
build validates it and recomputes the seal before rendering; an edited figure fails the build
rather than reaching you. Three rules do the work, and none of them is a promise:
- Every figure declares who has to act for it to move. Not a label we chose per page — a required field, checked by the same validator that seals it.
- A document with no figure on the outside half does not validate. The subset this page renders was cut by a tool; had that tool dropped the witness count, the format would have refused the result instead of emitting a shorter page.
- The tables above are not ours. They come from the vendored renderer every property shares, which emits both halves or throws — so this page cannot start showing only the flattering one, however the framing around it changes.