services/backend/README.md documents local setup, but there's no top-level architecture doc tying the three pieces together (contracts ↔ backend indexer/auth ↔ frontend) — someone new to the repo has to piece together the data flow (Soroban events → indexer → Postgres → /streams → analytics.service.ts → GraphQL → UI) from source.
To do: add a short architecture doc (docs/ARCHITECTURE.md) with a diagram or ASCII flow of how a payment-stream event goes from an on-chain contract call to showing up in the dashboard, and how the SEP-10-inspired auth challenge/verify flow works end to end.
services/backend/README.mddocuments local setup, but there's no top-level architecture doc tying the three pieces together (contracts ↔ backend indexer/auth ↔ frontend) — someone new to the repo has to piece together the data flow (Soroban events → indexer → Postgres →/streams→analytics.service.ts→ GraphQL → UI) from source.To do: add a short architecture doc (
docs/ARCHITECTURE.md) with a diagram or ASCII flow of how a payment-stream event goes from an on-chain contract call to showing up in the dashboard, and how the SEP-10-inspired auth challenge/verify flow works end to end.