Learn the architecture
Start with the decisions the platform must protect: who a Party is, which source owns a Project, which memberships have been observed, and what evidence permits an operation. Then follow those decisions through persistence and delivery.
Learning path
- Strategic DDD: language, ownership and bounded contexts.
- Tactical DDD: entities, values, aggregates and invariants.
- Hexagonal architecture: ports, adaptors and composition.
- CQRS: commands, queries and revision-aware views.
- Event-driven architecture: facts, contracts and reactions.
- Consistency and delivery: transactions, receipts, outboxes and recovery.
- Event sourcing: choosing the authoritative persistence model.
- Testing and exercises: evidence for each architectural claim.
The theory is adapted from the multilingual architecture reference; see
attribution and source revision. Code excerpts are extracted at
build time from this checkout. The examples use Party Governance and Project from
the reviewed integration/current baseline. They illustrate specific boundaries and preserve
the contexts' documented limitations.
For implementation rules, consult DDD.md, ARCHITECTURE.md and the owning context README.
Page source
Source snapshot ยท Revision f928834c8.