The present tense. The recurring, witnessed observances Flashy Financial keeps — ritual/1. An agent observes each one and a human consecrates it; unwitnessed practice moves nothing. ritual/1 is unpublished until its first adopter, so this page states the practice rather than sealing it.
The rites
Each names its cadence, the agent that witnesses it and the human who consecrates it.
The record refresh
The backlog/1 and directory/1 fragments are re-emitted so a month-old intention cannot read as current. Items decay; the fragment keeps up.
The ship seal
What shipped is derived from the repository’s own history and sealed as shipped/1, each entry classified by kind — the past tense, which never decays.
The charter review
The charter and the flashyos/1 handshake are re-read against what the property actually serves, and the review date is stamped where every surface reads it.
The settlement seal
When the rails are live, a cross-property movement seals to the public record at flashynetwork.com, where a stranger can verify it offline. Named here before it runs.
Why rites, not a cron list
A schedule says when a job runs; a rite says who answers for it. The estate’s record is only as trustworthy as the practice that produces it, so each observance names a human consecrator — the machine observes, the person stands behind it.
When ritual/1 is adopted across the estate, these become sealed observances with a verifiable last-run; until then they are stated here as a commitment, measured by the fragments they produce (the roadmap and the ledger refresh daily; the ship log seals on every push).