Context
When Epic 3 ships AES-256-GCM as a second encryption backend, the #1 user question will be "which backend should I choose?" A decision matrix comparing Fernet vs AES-256-GCM on security level, performance, compliance requirements, and use cases will reduce support burden and guide adoption.
Scope
New documentation page with:
- Feature comparison table (algorithm, key size, mode, NIST compliance level)
- Performance comparison (link to published benchmarks from Story 3.4)
- Decision flowchart or matrix
- Migration guidance between backends
Dependencies
- Story 3.1 (AES-256-GCM backend exists)
- Story 3.4 (benchmarks published)
Timing
Should ship after Epic 3 stories 3.1 and 3.4 are complete, before or alongside Story 3.3 (multi-backend coexistence).
Context
When Epic 3 ships AES-256-GCM as a second encryption backend, the #1 user question will be "which backend should I choose?" A decision matrix comparing Fernet vs AES-256-GCM on security level, performance, compliance requirements, and use cases will reduce support burden and guide adoption.
Scope
New documentation page with:
Dependencies
Timing
Should ship after Epic 3 stories 3.1 and 3.4 are complete, before or alongside Story 3.3 (multi-backend coexistence).