Record format
rites-protocol
ritual/1 — the Trust layer’s present tense: the recurring, witnessed, consequence-bearing act between backlog/1 (the future) and shipped/1 (the past). Liturgies and the observances performed against them, climbing a performed → witnessed → consecrated ladder by transition, never by assertion.
version 0.1.0 · measured 2026-10-19 from a checkout · source: Rites-Network
node vendor-ritual.mjs check ritual.fragment.json — dependency-free; not on npmFour refusals outrank everything: agents observe and humans consecrate (consecration.by is a person/ and nothing else); unwitnessed practice moves nothing (a witness signs with a basis of their own — a copy of the performer’s evidence is one source counted twice); an observance carries no value or standing (money words refused at any depth); and the log is append-only, a correction being a new void observance.
The anti-metric: raw observance volume is the number a faucet inflates, so metrics() ships witnessed and consecrated with the raw count, project() carries a note a renderer may not drop, and /adoption.html renders a sealed tally/1 document rather than a flattering figure.
Edge cases — each one paid for once
A calendar that shows a rhythm breaking is the format working
Rites-Network keeps its own ritual/1 record — the daily-office liturgy — and it is currently not being kept: every scheduled run 2026-09-24 to 09-28 failed within five seconds. The fragment cites the last office a run actually performed and does not paper over the gap with an observance no run performed.