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 same day the join kit ships in the one vendored file — init, liturgy, observe, witness, consecrate, and check over the network — org/flashyos publishes its first liturgy, the Daily Office, and this domain begins serving its calendar at /.well-known/ritual.json.