Evidence level: historically reviewed source and owner proposals; not freshly tested or certified for production.
Design and implementation invariants
- Redis catalog and cache values are reconstructible; balances, holds, payment credits and idempotent purchase facts belong to YSQL owners.
- ACL and cache contracts should prevent accidental escalation of producer or consumer authority.
Verification still required
- Verify live Redis ACLs, connection behavior and cache rebuild after restart; in-memory tests prove only isolated logic.
- Do not turn Redis into an authoritative financial ledger or persist broad secrets in cache keys.
How to update
When the owner changes implementation or contract behavior, update this page and the relevant service interfaces. For cross-service changes, also update the platform interface map or decision register. State the actual verification performed; do not inherit historical pass claims without fresh evidence.