Architecture

Documented design boundaries

The following is explanatory architecture context within the scope and limitations of CLM-010.

• Research code emits intents and cannot access production credentials, risk-limit storage or execution networks.
• Risk approval and exposure reservation are one atomic domain operation.
• Order, position/risk and financial books are separate governed books.
• Financial corrections use compensating entries; event history is evidentiary and is not itself accounting authority.
• Unknown orders require reconciliation before recovery or retry.
• Paper simulation has no live route or production capability.

Phase decomposition

Phase 1A

Contracts, checked domain types, order-state machine, atomic risk reservation, governed-ledger primitives, executable policy and invariant assurance.

Phase 1B

Deterministic market replay, paper execution, fills, position/financial posting, reconciliation, kill/recovery drills and replay evidence.

No strategy, AI or live/shadow connectivity may bypass either gate.

Architecture decisions

Material architectural choices are recorded as Architecture Decision Records (ADRs). Each ADR states the decision, alternatives considered, consequences, status, owner and independent approval. A proposed ADR is not an implementation approval.

• ADR-0001: Modular-monolith boundary — Proposed
• ADR-0002: Event persistence — Proposed
• ADR-0003: Arithmetic representation — Proposed
• ADR-0004: Reservation consistency — Proposed
• ADR-0005: Ledger authority — Proposed
• ADR-0006: Schema governance — Proposed
• ADR-0007: Replay determinism — Proposed
• ADR-0008: Dual public web origins and evidence-gated publication — Proposed

Source-of-truth order

1. Approved policy and legal requirements.
2. Architecture authority and approved ADRs.
3. Versioned contracts.
4. Executable code and tests.
5. Reference studies and explanatory documents.

Where sources conflict, implementation stops until the conflict is recorded and resolved through an ADR.