Architecture
Olly's architecture is documented in layered C4 model views generated from a single Structurizr DSL, supplemented by dynamic process flows and an InFORM-aligned coverage map. Start with the level that matches the question you are trying to answer.
| What it is | Best for | Open | |
|---|---|---|---|
| C4 L1 | System landscape | Stakeholders, onboarding, scope check | Business Landscape |
| C4 L2 | Container views per capability | Engineers wiring services together | Container Views |
| Dynamic views | Cross-capability sequence flows | Walking a business process end-to-end | Business Processes |
| Coverage | InFORM L1-L3 process map | Gap analysis, roadmap planning | Process Coverage |
Other diagrams
Per-service ownership, ports, databases, and sync vs async edges across the Go monorepo.
Choreography-based sagas, per-service topics, versionless JSON event envelopes, and outbox-driven publishes.
OIDC/PKCE flows, JWT validation, OPA policy points, and secret rotation via OpenBao.
Original system overview deck - build-vs-buy, dev workflow, coding guidelines, triage algos.
GKE in europe-west2, Cloud SQL CMEK, Strimzi Kafka, Memorystore, and network layout.
Entity-relationship diagrams for claims, billing, eligibility, enrollment, policy-admin, provider, and support.
How this is generated
The C4 L1, L2, and dynamic views are exported from a single source of truth - /root/olly/docs/architecture/workspace.dsl - via the Structurizr CLI. Running regen.sh re-validates the DSL, rebuilds the static Structurizr site at structurizr.dev.hiolly.com, and refreshes the Mermaid blocks embedded in the VitePress pages above. The static HTML decks under /arch/* and the per-service ERDs under /arch/erd/* are hand-authored and rsynced into public/arch/ at build time.