diff --git a/.claude/rules/stack-and-commands.md b/.claude/rules/stack-and-commands.md
index dc53ac6..a422e97 100644
--- a/.claude/rules/stack-and-commands.md
+++ b/.claude/rules/stack-and-commands.md
@@ -1,19 +1,20 @@
 ## Stack
 
-<!-- TODO: Fill in language, frameworks, and key dependencies -->
-- **Language:**
-- **Key deps:**
+- **Language:** Markdown-first registry and planning repo (no application runtime yet)
+- **Key deps:** State Hub ADR-001 workplans, `registry/indexes/capabilities.yaml`
 
 ## Dev Commands
 
 ```bash
-# TODO: Fill in the standard commands for this repo
+# Orient (offline-safe)
+cat .custodian-brief.md
+cat INTENT.md
+cat SCOPE.md
+ls workplans/
 
-# Install dependencies
+# After workplan or registry edits — from ~/state-hub
+make fix-consistency REPO=coordination-engine
 
-# Run tests
-
-# Lint / type check
-
-# Build / package (if applicable)
+# Sanity-check markdown / registry edits
+git diff --check
 ```
diff --git a/SCOPE.md b/SCOPE.md
index d48e39a..815d445 100644
--- a/SCOPE.md
+++ b/SCOPE.md
@@ -1,137 +1,31 @@
 # SCOPE
 
-> This file helps you quickly understand what this repository is about,
-> when it is relevant, and when it is not.
-> It is intentionally lightweight and may be incomplete.
+> Lightweight boundary for agents and contributors.
 
 ---
 
 ## One-liner
 
-<!-- Describe the purpose of this repository in one precise sentence. -->
-<!-- Example: "Provides a lightweight event router for Kubernetes-native systems." -->
+Framework for goal-driven digital coordination as communication.
 
 ---
 
 ## Core Idea
 
-<!-- What is the main capability or idea behind this repository? -->
-<!-- What problem does it try to solve? -->
+coordination-engine captures coordination models, specs, and registry entries for how actors align on shared goals.
 
 ---
 
 ## In Scope
 
-<!-- What this repository is responsible for. -->
-<!-- Be explicit and concrete. -->
-
--
--
--
+- Coordination specs, history, and registry indexes
+- State Hub workplans and agent instructions
+- Capability registration when coordination patterns stabilize
 
 ---
 
 ## Out of Scope
 
-<!-- What this repository deliberately does NOT do. -->
-<!-- This is often more important than "In Scope". -->
+- Runtime orchestration engine implementation (future repos)
+- Replacing issue trackers or chat systems
 
--
--
--
-
----
-
-## Relevant When
-
-<!-- When should someone consider using or exploring this repository? -->
-
--
--
--
-
----
-
-## Not Relevant When
-
-<!-- When should someone ignore this repository? -->
-
--
--
--
-
----
-
-## Current State
-
-<!-- Rough indication of maturity. No strict format required. -->
-
-- Status: <!-- e.g. concept / experimental / active / stable / deprecated -->
-- Implementation: <!-- e.g. idea / partial / substantial / complete -->
-- Stability: <!-- e.g. unstable / evolving / stable -->
-- Usage: <!-- e.g. none / personal / internal / production -->
-
-<!-- Add any notes that help set expectations. -->
-
----
-
-## How It Fits
-
-<!-- Where does this repository sit in the bigger picture? -->
-
-- Upstream dependencies:
-- Downstream consumers:
-- Often used with:
-
----
-
-## Terminology
-
-<!-- Terms that are important to understand this repo. -->
-<!-- Especially useful if naming differs from other repos. -->
-
-- Preferred terms:
-- Also known as:
-- Potentially confusing terms:
-
----
-
-## Related / Overlapping Repositories
-
-<!-- List repositories that have similar or adjacent responsibilities. -->
-<!-- Helps detect duplication and navigate the ecosystem. -->
-
-- <repo-name> — <!-- how it relates -->
-
----
-
-## Getting Oriented
-
-<!-- If someone decides to look deeper, where should they start? -->
-
-- Start with:
-- Key files / directories:
-- Entry points:
-
----
-
-## Provided Capabilities
-
-<!-- What can this repo's domain provide to other domains on request? -->
-<!-- Each capability block is parsed by the state-hub capability catalog ingest. -->
-<!-- Remove the examples and add your own, or leave empty if none. -->
-
-<!--
-```capability
-type: infrastructure
-title: Example capability title
-description: What this capability provides, in one or two sentences.
-keywords: [keyword1, keyword2, keyword3]
-```
--->
-
----
-
-## Notes
-
-<!-- Anything else worth knowing. Keep it short. -->
diff --git a/workplans/COORDINATION-WP-0001-statehub-bootstrap.md b/workplans/COORDINATION-WP-0001-statehub-bootstrap.md
index fc51fde..b4f7391 100644
--- a/workplans/COORDINATION-WP-0001-statehub-bootstrap.md
+++ b/workplans/COORDINATION-WP-0001-statehub-bootstrap.md
@@ -4,7 +4,7 @@ type: workplan
 title: "Bootstrap State Hub integration"
 domain: communication
 repo: coordination-engine
-status: ready
+status: finished
 owner: codex
 topic_slug: communication
 created: "2026-06-22"
@@ -20,11 +20,14 @@ Coordination engine for inter-repo workflows.
 
 ```task
 id: COORDINATION-WP-0001-T01
-status: todo
+status: done
 priority: high
 state_hub_task_id: "95769b93-99ce-4cbd-be90-a41dbb87fda0"
+
 ```
 
+Result 2026-06-22: Filled SCOPE.md from INTENT.
+
 Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
 Replace generated placeholders with repo-specific facts where needed.
 
@@ -32,11 +35,14 @@ Replace generated placeholders with repo-specific facts where needed.
 
 ```task
 id: COORDINATION-WP-0001-T02
-status: todo
+status: done
 priority: high
 state_hub_task_id: "1c1930c6-8bd7-4979-b0a6-cfa476674129"
+
 ```
 
+Result 2026-06-22: Registry-oriented dev workflow documented.
+
 Identify the repo's install, test, lint, build, and run commands. Add or refine
 those commands in the agent instructions so future coding sessions can verify
 changes confidently.
@@ -45,11 +51,14 @@ changes confidently.
 
 ```task
 id: COORDINATION-WP-0001-T03
-status: todo
+status: done
 priority: medium
 state_hub_task_id: "f74ef97e-8f0a-4d54-b17c-12dcb68ac3f1"
+
 ```
 
+Result 2026-06-22: Created COORDINATION-WP-0002.
+
 Create the first implementation workplan for the repository's most important
 next change. After workplan file updates, run from `~/state-hub`:
 
diff --git a/workplans/COORDINATION-WP-0002-coordination-model-spec.md b/workplans/COORDINATION-WP-0002-coordination-model-spec.md
new file mode 100644
index 0000000..f718a2a
--- /dev/null
+++ b/workplans/COORDINATION-WP-0002-coordination-model-spec.md
@@ -0,0 +1,28 @@
+---
+id: COORDINATION-WP-0002
+type: workplan
+title: "Coordination model specification baseline"
+domain: communication
+repo: coordination-engine
+status: ready
+owner: codex
+topic_slug: communication
+created: "2026-06-22"
+updated: "2026-06-22"
+state_hub_workstream_id: "2b62c9df-577d-45ce-81a7-cf343e2fb6b0"
+---
+
+# Coordination model specification baseline
+
+Draft the first coordination ontology and message lifecycle spec for the engine.
+
+## Author coordination spec v0.1
+
+```task
+id: COORDINATION-WP-0002-T01
+status: todo
+priority: high
+state_hub_task_id: "0ece010b-4597-4ae9-b77d-26a3ff8c906f"
+```
+
+Write `spec/coordination-model-v0.1.md` covering actors, goals, commitments, and observation loops.