Public HTTPS entry point for the partial applications.
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.
Frontend ⇄ Backend · API
Frontend / Backend ⇄ Keycloak · Identity
System-level only. Sub-application diagrams can carry implementation detail without duplicating this overview.
FOLLOW THE PATH
Connections, made explicit.
Routes traffic to each application behind the shared entry point.
Application API interaction; protocol details remain open.
Identity-related communication. Detailed flows belong in the authentication specification.
Domain persistence. The database product is undecided.
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.
Decide together
Ingress, identity, backend stack and database decisions update this overview in the same change set.
Remove resolved markings
When a component is decided, its undecided label and dashed border are removed together.
Keep one system view
Reference the text diagram from the architecture overview; let deeper diagrams stay with their sub-applications.