Ritual Protocol: a key as an action, not an object

Ritual Protocol: a key as an action, not an object Every secret storage system is only as secure as the storage itself. Someone steals your password database — they steal everything. Someone compromises your keystore — they compromise everything. You can encrypt the storage, split keys, add authentication factors — but the fundamental problem remains: the key exists as an object, and objects can be stolen. Ritual Protocol takes a different approach. The key is not stored. It is reproduced through a sequence of actions — a ritual. Same actions, same parameters — same 32 bytes out. Every time. No storage — no attack vector tied to its compromise. How it works A ritual is an ordered set of rites. Each rite has a type and parameters. Order matters: sequences [A, B, C] and [C, B, A] produce different keys. Rite types V1 defines six rite types. They can be combined in any order and repeated — each repetition increases entropy. The rites are intentionally varied — a text string, a symbol sequ