Three raw files, served here for machines and implementers alike. The schema answers what a fragment is shaped like; the corpus answers what an implementation must refuse; the spec says why. Nothing on this page is retyped — the counts below are read from the files they describe.
The format in prose: the shape, the four refusals, the ladder, and the boundary with reward/1 — the file the package itself ships.
The shape, machine-checkable. The schema validates structure; the four refusals live in the validator and the corpus, because a schema cannot see a citation loop.
One case per rule, each naming the rule it exercises and the verdict required. An implementation in any language proves itself by agreeing with every verdict — the corpus is the count, and this page reads it rather than restating it.
22 cases — 4 ok, 18 reject. Schema id https://flashyos.com/schemas/ritual-1.schema.json.
oka performed observance with evidence is validoka witnessed observance with a second party's own basis is validokan empty calendar is honest and validoka void observance naming what it supersedes is validrejecta consecration by an agent is refused — humans consecraterejecta consecrated observance with no witness block is refusedrejecta self-witness is refused — the witness is the performer's principalrejecta witness without its own basis is refused — a copy is a citation looprejectan observance carrying an amount is refused — no value in this formatrejectan observance carrying a streak is refused — standing is derived elsewhererejecta human performer is refused — a person's own act is work, not observancerejectan observance of a liturgy the fragment does not hold is refusedrejectan observance with no evidence is refused — this format carries no claimsrejectrecorded before the act is refused — the holding/1 lag rulerejecta performed observance smuggling a witness block is refused — the ladder is climbed by transitionrejecta duplicate observance id is refused — append-onlyrejecta void naming nothing is refused — a deletion with better mannersrejecta liturgy published by an org is refused — a person answers for the askingrejectan unknown cadence is refused — a new rhythm is a decisionrejecta witnessed observance smuggling a consecration block is refusedrejecta money word at the fragment's top level is refused — any depth includes zerorejecta live observance that supersedes another is refused — a correction is a voidThe reference implementation is the vendored file itself — dependency-free, and the npm entry point of @flashyos/ritual when it publishes. How to join with it is on the overview; the ladder is walked on how it works.