recording-architecture-decisions

Create an architecture decision record by following the guided workflow to capture decisions, enforce ADR conventions, and route the file to the correct ownership surface, preserving rationale alongside the current-state baseline.

Amend or supersede an ADR by applying baseline-sync constraints and helper-backed write paths to ensure correct file placement, consistent naming, and traceability across project surfaces, avoiding stale baselines or misapplied changes.

Baseline-sync closure for decision logs records durable architecture changes by enforcing baseline-sync constraints, filtering memory, and routing work to the correct ownership surface to prevent stale baselines and maintain traceability.

You need an established ownership surface, such as docs/adr or docs/aegis/adr, to correctly route architecture decisions, enforce ADR conventions, and ensure proper file placement and naming when creating or amending decision logs.

Evaluate an architecture decision log when you need to assess existing ADRs or baseline-sync records, applying guardrails to avoid stale baselines, verify current-state alignment, and ensure decisions are correctly documented across project surfaces.