docs: ADR for zero-knowledge encryption Phase 1
Records the decision: client-side AES-256-GCM, double-PBKDF2 auth/enc-key split, server-as-blind-store, in-memory key lifecycle, and Phase 1 limitations (forgotten password = data loss; Phase 2 recovery wrapping deferred).
This commit is contained in:
parent
1301473bfe
commit
d7d09482da
2 changed files with 70 additions and 0 deletions
|
|
@ -18,6 +18,7 @@ the documentation reconciliation. They are historical context, not current specs
|
|||
| [backend-deployment-constraints.md](./backend-deployment-constraints.md) | Deployment requirements (Solaria, Docker) |
|
||||
| [mobile-health-frameworks-data.md](./mobile-health-frameworks-data.md) | HealthKit / Health Connect data-type reference (for future mobile work) |
|
||||
| [android-health-connect-data-types.md](./android-health-connect-data-types.md) | Android Health Connect data types |
|
||||
| [zero-knowledge-encryption.md](./zero-knowledge-encryption.md) | Client-side zero-knowledge encryption (AES-256-GCM, double-PBKDF2, Phase 1) |
|
||||
|
||||
> **Note**: Where a decision diverges from the implemented code (e.g. state
|
||||
> management), the code is the source of truth and the ADR is kept only as
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue