agicash-wallet-architecture

Agicash Wallet Architecture

Read docs/architecture.md for the full architecture overview with diagrams.

Component Summary

Four components — understand their boundaries before making changes:

When to Consult the Architecture Doc

• Adding a new server route or API endpoint — check what the server can and cannot access (no Open Secret, only non-sensitive DB data via service role key)
• Working with encryption/decryption — understand the client-side-only encryption model and why the server cannot decrypt
• Modifying auth or key derivation — understand the Open Secret → Supabase JWT flow
• Adding or changing Realtime subscriptions — understand the client ↔ DB realtime pattern
• Deciding server vs client for new functionality — the architecture doc clarifies the boundary: if it needs seeds, keys, or decrypted data, it must be client-side