# Rites Protocol — ritual/1 > The present tense of the record. backlog/1 says what an organisation intends. shipped/1 says what it did. ritual/1 is the tense between them: the recurring, witnessed, consequence-bearing act — what an organisation practises, on a rhythm a stranger can check. Agents observe. Humans consecrate. Unwitnessed practice moves nothing. This site is the standalone home of ritual/1, a record format of the Gord & Flashy estate. No independent adopter exists yet and the package is unpublished until the first one; the vendored implementation travels by copy. ## Pages - [The format](https://rites.network/index.html) — the three tenses, the ladder, the four refusals, three integration doors, and what does not exist yet. - [How it works](https://rites.network/how-it-works.html) — one observance walked up the ladder in five steps. - [The spec](https://rites.network/spec.html) — ritual/1 rendered; the raw Markdown is below. - [Changelog](https://rites.network/changelog.html) — dated entries, real events only. - [Devlog](https://rites.network/devlog.html) — the devlog/1 record, derived from commit history, each entry linked to its own leaf on the estate transparency log. ## Machine artifacts (byte copies of the versioned files) - [/spec.md](https://rites.network/spec.md) — the specification, raw. - [/ritual-1.schema.json](https://rites.network/ritual-1.schema.json) — JSON Schema for the fragment shape. - [/conformance/corpus.json](https://rites.network/conformance/corpus.json) — 23 cases; a non-JS implementation proves itself by agreeing with every verdict. - [/.well-known/ritual.json](https://rites.network/.well-known/ritual.json) — this property's own ritual/1 calendar, served whole; check it with `node vendor-ritual.mjs check https://rites.network`. - [/.well-known/devlog.fragment.json](https://rites.network/.well-known/devlog.fragment.json) — this repository's own devlog/1 record, served whole, byte for byte of the committed fragment. ## Web 4 Web 4 is the agentic internet: a stack of open protocols through which software agents discover, identify, authorize, trust, transact with and audit one another. Hub: https://github.com/FlashyLabs/web4 Rites Protocol is layer 4 of the stack — trust ("Should I deal with you?") — contract ritual/1. ## Check a fragment node vendor-ritual.mjs check ritual.fragment.json The format's home is flashyos, packages/ritual. This site renders it; it does not fork it.