HISTORIC ATLAS / MODEL NOTEBOOKThe diagram contract ↗
DATA MODEL / PHYSICAL SCHEMA

A shared picture.
A reviewable source.

DRAFT SPECIFICATION

Keep the database diagram beside the migrations. Every table, every column, every relationship.

Illustrative fixture, not the application schema. This requirement provides no migration files. The sample below demonstrates the diagram conventions without asserting actual table names or relationships.
AVARC SCOPE · Select a table to inspect
1 → many───▷owner_id
CHANGE TOGETHER

The migration
is the source of truth.

  • 01 / Physical, not conceptual. Match tables created by migrations, rather than the logical area model.
  • 02 / One change set. Every new or changed Flyway migration updates the diagram in the same change.
  • 03 / Explicit annotations. Mark generated columns and fields the application does not map.
  • 04 / A focused boundary. Include every avarc table, its typed columns, keys and relations. Exclude Keycloak and PostGIS tables.
  • 05 / Linked from the areas. Locations and Users data-model sections reference datamodel-diagram.md.
TEXT FIRST / DATAMODEL-DIAGRAM.MD

Mermaid erDiagram source belongs in a fenced mermaid block. GitHub renders the text directly; only source is committed. This page's diagram is an original HTML visualization of the fixture, not a live Mermaid renderer.