code: remove dead AccessClaims struct in backend/src/auth/claims.rs
docs: product/encryption & persona docs badly out of sync with implemented ZK encryption
All four docs in this issue are now done (uncommitted, in the working tree):
- ✅
docs/product/encryption.md— full rewrite to the implemented wrapped-DEK / Web Crypto model - ✅…
docs: product/encryption & persona docs badly out of sync with implemented ZK encryption
design: multi-person / family / caregiver data sharing under zero-knowledge encryption is unsolved
Correction to my earlier comment (and to issue #3 body): I wrote that the JWT carries family_id + permissions. That'''s wrong.
The real access-token Claims (backend/src/auth/jwt.rs)…
design: multi-person / family / caregiver data sharing under zero-knowledge encryption is unsolved
Started the ADR draft at docs/adr/multi-person-sharing.md (uncommitted, in the working tree).
It records the decision forced by the constraints above (per-profile DEK + X25519 envelope), spells…
docs: product/encryption & persona docs badly out of sync with implemented ZK encryption
Ok to go with the proposed fix
design: multi-person / family / caregiver data sharing under zero-knowledge encryption is unsolved
Synthesis from @alvaro's answers (2026-07-18)
The constraints rule out most options and force a concrete architecture.
Ruled out
- (b) family-level shared key — incompatible with…
design: multi-person / family / caregiver data sharing under zero-knowledge encryption is unsolved
Answers to questions plus extra info
- parent and spouse each will have their login, and they may not even be the same family. Divorced parents with each their own family may want to share the…
docs: product/encryption & persona docs badly out of sync with implemented ZK encryption
design: multi-person / family / caregiver data sharing under zero-knowledge encryption is unsolved