Updates & releases

Each release ships with a manifest signed by our Ed25519 release key. The core verifies the signature before accepting anything. The public key is published at /api/public/release-key so you can verify a manifest independently of us. If we ever rotate the key, the new one appears there and the change is announced to contract holders.

• Optional — improvements. Take it whenever suits you.
• Advised — meaningful protection gains. Recommended within the current cycle.
• Critical — closes an exploited or exploitable gap. Carries a deadline.

Releases are rolled out in stages rather than to everyone at once. Your account shows which release your install is on and whether a newer one is targeted at you. Nothing is pushed into your codebase — you upgrade the package yourself, which is what keeps it your deployment.

When a critical release passes its deadline and an install is still behind, our ingest endpoint answers 426 Upgrade Required instead of accepting the report. That is deliberately loud: the install keeps protecting your site locally, but it stops being counted as current until it is upgraded.

Recovery is simply upgrading the package and restarting. The next report is accepted and your fleet status returns to current within a cycle — no manual reset from us.

Open /account/install. It shows the installed release each of your systems is reporting, the current published release, and whether any deadline applies to you.