Docs

Architecture Overview

High-level module boundaries and reliability rules for Megami.

Document Meta
Path: /docs/architecture
Updated: March 22, 2026
Sections: 2

Megami is organized as an explicit domain-first system:

  • packages/domain: deterministic mechanics and invariants
  • packages/integrations: adapter layer for external APIs and providers
  • packages/database: schema, query boundaries, and transactional enforcement
  • apps/*: delivery surfaces that orchestrate and render outcomes

Transaction-Critical Flows

These actions must remain transaction-backed:

  1. Print minting
  2. Relationship transitions
  3. Steal and defense resolution
  4. Economy debit and credit operations

Auditability

Keep immutable history records for socially critical state transitions.