Ovahol backend architecture

This directory records the intended architecture of the Ovahol backend and the decisions that constrain future implementation work.

The migration from the legacy layer-first structure to a modular monolith is complete. All 13 business modules are in place. Cross-module coupling is enforced by architecture tests in every module.

Documents

• Contributor guide — start here if you are adding new code. Covers module structure, import rules, the reader/ pattern, sqlc workflow, and the near-term roadmap.
• Modular monolith — target structure, infrastructure layers, and migration principles.
• Module map — what each module owns and the four infrastructure layers (platform/, adapters/, common/, shared/).
• Dependency rules — allowed and forbidden imports, enforcement via architecture tests.
• Terminology — canonical business and architectural names.
• Architecture decisions — ADRs governing this work.