2.1 KiB
ADR-0020 — Architecture Generation 2 governance adoption
Status: Accepted by ARCH-GEN2-000
Date: 2026-08-29
Scope: Architecture and governance only; no runtime or schema migration.
Decision
Assistant adopts the documents under docs/DOMOVOY_CONSTITUTION.md,
architecture/GEN2_TARGET_ARCHITECTURE.md,
architecture/GEN2_CANONICAL_DATA_MODEL.md,
development/GEN2_MIGRATION_MAP.md,
development/GEN2_MASTER_PLAN.md, and the execution contract as the
canonical Architecture Generation 2 governance basis.
The existing V1 implementation remains the rollback and compatibility baseline. This decision authorizes subsequent, separately accepted Gen2 packets to introduce the World, Configuration, and SELF bounded owners and Gen2 migrations, subject to explicit ownership, schema, contract, and rollback decisions in those packets. It does not create those owners or change canonical runtime state in this task.
Authority and execution order
The Gen2 constitution and accepted architecture decisions govern the Gen2 program. The target architecture, canonical data model, migration map, master plan, execution contract, task index, and individual task packet are interpreted in that order. A lower-level packet cannot silently weaken a higher-level invariant or reorder the task index.
Every Gen2 task starts from gen2-integration, uses the active task pointer,
and passes the declared FAST/MILESTONE/FULL gate before merge. ARCH-GEN2-000
is the architecture adoption root accepted against the PRE baseline;
GEN2-001 and later tasks are not accepted by this decision and require
separate execution.
Invariants preserved
- No new canonical owner, cross-module dependency, privilege, database role, third-party dependency, runtime writer, event, or migration is introduced.
- Existing Authority → Commit → Executor boundaries remain mandatory.
- Memory remains a rebuildable retrieval fabric, World is not a generic truth owner, and SELF is not a monolithic orchestrator.
- The
domovoy-pre-gen2baseline tag remains immutable and is the rollback point until a later migration task explicitly establishes another one.