Bounded Contexts
One-line summary per context. Click through for aggregates, state machines, events, and public API.
| Context | Purpose | Overview |
|---|---|---|
access-policy | Access control and permission management | overview |
alerts | Operational alerting for anomalies | overview |
cex-wallets | CEX integrations and wallet orchestration | overview |
common | Shared domain abstractions, logger, event system | overview |
database | Prisma schema and migrations | overview |
funds | Daily funds accounting | overview |
partners | Partner accounts, dues, payment runs | overview |
providers | Blockchain and RPC provider integrations | overview |
rates | Pricing, pairs, fees, market data | overview |
secrets | Encryption and secret handling | overview |
shifts | Exchange shift lifecycle and transfers | overview |
stats | Statistics and analytics | overview |
sw-jobs | BullMQ job scheduling | overview |
users | User management, auth, 2FA | overview |
wallets | Crypto wallet operations | overview |
How to add a new context doc
Use the bounded-context template. Document the state machines owned by the context in ../state-machines/ (transversal location).
