DRAFT ARCHITECTURE

Architecture / System-level diagram

KNOW HOW THE PIECES FIT

A map of the system.

From the browser to the data. A reviewable view of what is known,
what is open, and what comes later.

Named component Undecided technology Post-MVPPresentation only · Not a live deployment
SYSTEM OVERVIEW / TOP TO BOTTOM
↓ HTTPS
↙ Frontend routeBackend route ↘
↓ AuthenticationPersistence ↓
┊ Planned connection to backend ┊

System-level only. Sub-application diagrams can carry implementation detail without duplicating this overview.

FOLLOW THE PATH

Connections, made explicit.

Browser → Web server

Public HTTPS entry point for the partial applications.

Web server → Frontend / Backend

Routes traffic to each application behind the shared entry point.

Frontend ⇄ Backend

Application API interaction; protocol details remain open.

Applications ⇄ Keycloak

Identity-related communication. Detailed flows belong in the authentication specification.

Backend ⇄ Database

Domain persistence. The database product is undecided.

MCP server ⇄ Backend

Planned post-MVP extension; connection details are not yet selected.

TEXT IS THE SOURCE OF TRUTH

Small diffs. Clear decisions.

This exact baseline is maintained in the model directory’s architecture-diagram.md. The browser overview is HTML/CSS; no rendered diagram image is maintained as the architecture source.

KEEP THE MAP CURRENT

Change the decision. Update the diagram.

1

Decide together

Ingress, identity, backend stack and database decisions update this overview in the same change set.

2

Remove resolved markings

When a component is decided, its undecided label and dashed border are removed together.

3

Keep one system view

Reference the text diagram from the architecture overview; let deeper diagrams stay with their sub-applications.