Directive 02 · sealed
The seal
The exact wording of the directive is published seven days before the equinox. Its hash is published now, so that afterwards anybody can check that the text they were given is the text that was sealed — including if they do not trust us.
SHA-256 of the sealed directive
5d0f8aaa e2d5209b acc46ad0 8887e19d 23093e73 c25c9848 4c9b4efc f361cf1f
How to check it yourself
When the directive opens on 2026-09-16 14:05:00 UTC, take its canonical form — each step as time⇥heading⇥detail, one per line, joined by newlines, encoded UTF-8 — and hash it:
printf '%s' "$DIRECTIVE" | sha256sumIf that does not produce the string above, something changed between the seal and the reveal, and you should say so loudly.
What is already known
The structure was never secret and is written on the front page: four seconds of an open vowel, one spoken name, ten seconds of silence. What is sealed is the precise wording — which words, in which order, translated into every language at once.
The same hash is displayed inside the app, computed independently on your own device from the copy shipped in the binary. Two computations, one number — if they ever disagree, trust neither.