docs: align top-level guidance with phase 1 baseline

AGENTS.md

@@ -2,15 +2,20 @@
 
 ## Scope of this repository
 
-This repository is in **phase 0**.
+Phase 0 is complete.
 
-The goal of this phase is to define:
+The repository now has:
+- a completed workflow and portability foundation from phase 0
+- accepted phase-1 technical decisions recorded through ADRs
+- enough documented guidance to support implementation work that follows the accepted baseline
+
+The goal of the current phase is to continue:
 - how development with Codex and custom agents works
 - how repository workflow works
-- how tasks are executed and closed
-- how the project remains portable across machines
+- how technical decisions are documented and applied
+- how implementation work follows accepted repository decisions
 
-This phase is **not** for deciding the product architecture or implementing application features.
+This repository is no longer limited to workflow/bootstrap work. Runtime, database, structure, workflow, and configuration baselines have already been accepted through ADRs and must guide future implementation tasks.
 
 Agents must optimize for:
 - repeatability
@@ -170,6 +175,14 @@ Never claim tests passed unless they were actually executed.
 
 ---
 
+## ADR Discipline
+
+Implementation work must follow accepted ADRs.
+
+Current accepted decisions live under `docs/adr/` and include the baseline runtime, structure, developer workflow, and configuration strategy. If a task depends on a new major technical choice, document or update the decision explicitly rather than relying on undocumented assumptions.
+
+---
+
 ## Documentation discipline
 
 Whenever behavior changes, update docs if relevant.
@@ -186,15 +199,9 @@ Do not let docs drift from actual workflow.
 
 ## Out of scope in phase 0
 
-Do not decide yet:
-- final application architecture
-- final domain model
-- runtime services beyond workflow tooling
-- database technology
-- ingestion strategy
-- feature list
+Phase 0 no longer blocks technical decision-making. Phase-1 baseline decisions have already been accepted.
 
-If a task drifts into product design, stop and ask for a separate explicit decision.
+Still do not treat product decisions as implicit. If a task drifts into new product scope or a major technical choice that is not yet documented, stop and ask for a separate explicit decision or ADR update.
 
 ---
 
@@ -208,4 +215,5 @@ Avoid:
 - speculative optimization
 - introducing tools that are not yet justified
 
-This phase is about building a clean development method first.
+This phase is about building a clean development method first.
+That method now extends to implementation work that follows the accepted ADR baseline.