# 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.

## 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) — 22 cases; a non-JS implementation proves itself by agreeing with every verdict.

## 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.