Rites Protocol

Changelog

A dated record
that grows

Real events only, each on the day it happened. Entries are appended, never edited — the same rule the format itself keeps.

ritual/1 ships, is audited the same day, and goes live

The format lands on main: the dependency-free vendored implementation, four refusals enforced in the validator and again in every transition, a JSON Schema, and a conformance corpus for non-JS implementations. An adversarial audit the same day found four leaks — block smuggling across states, vocabulary skipping depth zero, live supersedes double-counting, a retyped count — and all four now answer REFUSED, each pinned by a corpus case. flashyos.com/ritual answers 200, measured.

The first consecration surface is built

RitualOS — incubating in the estate — stages the first product surface over ritual/1: a treasury-admin page that renders the calendar, shows the ladder per observance, and offers Consecrate only where the format permits it. The vendored validator is the one that answers; the page cannot be more permissive than the file.