Architecture
This section documents the structural design of the Platform: how responsibilities are divided, how systems interact, and how complexity is constrained as the ecosystem grows.
Rather than describing individual implementations in isolation, these pages focus on relationships, boundaries, and tradeoffs — the parts of the system that are hardest to change later.
System Overview
The System Overview presents the Platform at its highest level. It explains how applications, platform packages, domains, and CI/CD workflows fit together, and why the Platform exists as a layer beneath product code rather than a centralized runtime.
This page is the best entry point if you want to understand what the Platform is before diving into specific architectural decisions.
Domain Model
The Domain Model explains how shared behavior is defined once and reused across frameworks and products. It introduces the distinction between domains (behavioral knowledge) and adapter packages (runtime-specific entry points), and shows how this separation prevents drift as the number of applications grows.
This page is where the core architectural philosophy of the Platform is made explicit.
Package Topology
Package Topology describes how domains, adapters, and applications depend on each other in practice. It documents the enforced dependency direction, change radius, and ownership boundaries that keep the system evolvable over time.
If you want to understand how the Platform avoids duplication, hidden coupling, and fragile shared code, start here.
How These Pages Fit Together
These documents are designed to be read in order:
System Overview — establish the mental model
Domain Model — explain responsibility boundaries
Package Topology — show how those boundaries are enforced
Together, they describe not just how the Platform is built, but how it is intended to scale.
Scope and Constraints
This section focuses on architecture, not implementation details.
It does not document individual APIs or functions
It does not describe CI/CD execution step-by-step
It does not duplicate the Platform case study
Those concerns live in their respective sections.