Account Nexus is a group of independently deployable services with explicit versioned interface and ownership boundaries. The code was migrated from a monolith; restored source and historical acceptance evidence do not establish production readiness.
Deployment model
- One independent runtime role per service, with its own code, contract, image, tests and rollback boundary.
- Initial design targets a single VPS, without cross-imports of another service’s private code.
- Documentation has 22 independent service sites and a separate platform site, isolated from application containers.
- Ingress, operator authority, provider lifecycle and provider API access are different security boundaries.
Data ownership
- YSQL: intended durable financial and purchase-intent store.
- Wallet: append-only ledger, holds, releases and verified credits.
- Commerce: customer purchase admission, orders and command records.
- Purchase Executor: guarded dispatch after an authoritative hold and committed intent.
- Redis: rebuildable cache, never the financial source of truth.
- Secrets Provisioner: master-key authority and scoped credentials.
Three logical database nodes on one VPS do not establish physical high availability.
Follow the interface map, purchase lifecycle, provider planes, and decision register. Each service has its own docs site.
Assurance limits
An approved design is not evidence of deployed integrations, final security review or N/N-1 compatibility.