docs: decide multi-person ZK sharing ADR; reconcile jwt/encryption docs (#4) #10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "docs/3-4-encryption-persona-docs-reconciliation"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The doc-reconciliation work from earlier in the session — stranded on this branch and never merged. Phase A1 (#6) and A2 (#9) both built on
main, which does not currently contain the multi-person-sharing ADR their code comments reference. This PR lands the decided design and the corrected docs.Contents
docs/adr/multi-person-sharing.md(NEW) — the decided ADR for per-profile DEK + X25519 envelope sharing. All five original open questions resolved 2026-07-18. Covers divorced-parents, pets, graduation, elderly-parent care; adds an admin permission tier. This is the design Phase A1/A2 implement and Phase B will build on.docs/product/encryption.md— full rewrite to the implemented wrapped-DEK / Web Crypto model (the old version described ZK encryption as 'planned').docs/adr/jwt-authentication-decision.md— rewritten to match the implementation (PBKDF2 not bcrypt, no Redis, token_version revocation, real Claims). Original aspirational content preserved in a History section.docs/product/PERSONA_AND_FAMILY_MANAGEMENT.md— 'Current reality' section added, old 'Implementation Status' marked superseded, encryption section corrected.docs/product/ENCRYPTION_UPDATE_SUMMARY.md→ archived todocs/archive/.docs/adr/README.md— index updated.Closes #4. Refs #3 (the ADR is the design of record for the sharing work tracked there).
Note
This branch was authored before A1/A2. It touches only docs, so there should be no merge conflicts with the code changes in #6/#9. If any of the doc rewrites contradict what A1/A2 actually shipped, I'll reconcile in a follow-up — but the ADR itself was written first and A1/A2 were implemented to match it.