diff --git a/AGENTS.md b/AGENTS.md
index 86eb0ea..97cba2c 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -2,7 +2,7 @@
 
 ## Repo Identity
 
-**Purpose:** Mail Address Semantics (MAS) v0.1 reference implementation: parser, statute discovery, pure policy, CLI, mail gateway and reference ticket service.
+**Purpose:** Mail Address Semantics (MAS) reference implementation and spec workbench (v0.1.1, v0.2 draft): parser, statute discovery, pure policy, generator, CLI, mail gateway, reference ticket service and Postfix integration profile. See INTENT.md (phase 2) and SCOPE.md.
 
 **Domain:** communication
 **Repo slug:** mail-address-semantics
@@ -97,13 +97,15 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
 
 ```bash
 uv venv && uv pip install -e '.[test]'   # install (only runtime dep: jsonschema)
-.venv/bin/pytest                         # full suite; offline apart from loopback fixture servers
+.venv/bin/pytest                         # full suite; offline apart from loopback fixtures; Postfix probe needs Docker
 .venv/bin/mas test                       # shared conformance corpus only
 ```
 
-`mas-v0.1-spec/` is the normative bundle. `mas_conformance/addresses.json` and
-`mas_core/schema/` are vendored copies, and tests fail if they drift from the
-bundle. Keep the boundaries: the parser does no I/O, policy is pure, and only
+`mas-v0.1-spec/` (v0.1.1) and `mas-v0.2-spec/` (draft) are the normative
+bundles. `mas_conformance/addresses.json`, `mas_conformance/statute_aware.json`
+and `mas_core/schema/` are vendored copies, and tests fail if they drift from
+the bundles. Spec changes need evidence, bundle fixtures and a `mas_core`
+implementation; record them in `docs/spec-change-proposals.md`. Keep the boundaries: the parser does no I/O, policy is pure, and only
 `mas_core/discovery.py` touches the network.
 
 ## Session Protocol