Public PreviewTesting header enabled

Open sitemapJump

/architecture

Architecture

Modular monolith with explicit domain boundaries.

Designed to evolve into a hybrid platform where only the right modules become services.

Module map Async workers

Design principles

Domain-first
01
Bounded contexts under src/domains keep logic coherent.
Audit by default
02
Critical actions produce immutable audit entries.
Async for heavy workloads
03
Risk, ingestion, reports, batch AI live in workers.
Sync for transactions
04
Orders, approvals, compliance decisions remain fast.
Event-driven when useful
05
Domain events power fanout and pipelines.
Service extraction later
06
Only split when scale/isolation is real.

Practical tradeoffs (what you get)

Capability	This approach	Typical pitfalls avoided
Single deploy early	Yes	No service mesh required
Clear module seams	Yes	No cross-domain shortcuts
Operational visibility	Yes	No blind async jobs
Scalable evolution	Yes	No premature splitting

Want to read the canonical doc?

This public page matches the architecture document used by the codebase.

Open docs index

Related pages

Cross-links across the public site for architecture, trust, specialty modules, and rollout.

Modules illustration

Modules

Bounded contexts for core and expansion capabilities.

Workers illustration

Workers

Async processing model for heavy workloads and reliability.

API Design illustration

API Design

Versioned contracts and workflow-oriented endpoints.

Observability illustration

Observability

Structured logs, trace context, and queue visibility.

Docs Index illustration

Docs Index

Top-level public documentation index.

Workflows illustration

Workflows

Lifecycle states for portfolio, compliance, orders, and settlement.