amadan
intent: point the recovery decision at its open question
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
1 file changed,
+7
−0
AGENTS.md+7 −0
Intent
diff --git a/AGENTS.md b/AGENTS.md| index 9b96db6..2e0a00a 100644 |
| --- a/AGENTS.md |
| +++ b/AGENTS.md |
| @@ -92,6 +92,13 @@ because paper is the only medium that is not the thing we are replacing. |
| Secondary reason, not the deciding one: the 1Password Emergency Kit means |
| this pattern is already understood by the audience. |
| +The key hierarchy is specified in `DESIGN.md`. **One decision remains open |
| +there** — whether a 128-bit Account Key is printed beside the recovery |
| +code — because it would change the promise that a passphrase alone gets |
| +you back in. Discussion 5. It does not block anything: the KEK branch is |
| +built with the input present and constant, so adopting it later is a |
| +re-wrap, not a redesign. |
| + |
| ### 3. Email exists only as a blind index (Paul, 2026-09-01) |
| Kass's shape: an HMAC under a server-held pepper. It proves identity for |