From c1a7a402a035af07e6a0d05782e8432722aa5b45 Mon Sep 17 00:00:00 2001 From: tegwick Date: Wed, 8 Jul 2026 16:35:46 +0200 Subject: [PATCH] docs: workplan-first agent guidance prose (CUST-WP-0055 T04) --- .claude/rules/workplan-convention.md | 2 +- INTENT.md | 6 +++--- SCOPE.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.claude/rules/workplan-convention.md b/.claude/rules/workplan-convention.md index aad1c0c..c01c6a9 100644 --- a/.claude/rules/workplan-convention.md +++ b/.claude/rules/workplan-convention.md @@ -46,7 +46,7 @@ fix-consistency. Do not edit or rename it. **Workplan** is the fleet term — see `the-custodian/canon/standards/workplan-terminology-fleet_v0.1.md`. -**Workstream** is legacy only: some API routes (`/workstreams/`), params +**Workplan** is legacy only: some API routes (`/workstreams/`), params (`workstream_id`), MCP aliases (`create_workstream`), and the frontmatter field above remain until `STATE-WP-0069` retires them via legacy-meter. Treat those identifiers as workplan IDs. Prefer `GET /workplans/` and `workplan_id` in new diff --git a/INTENT.md b/INTENT.md index a38a645..2e54633 100644 --- a/INTENT.md +++ b/INTENT.md @@ -22,7 +22,7 @@ The engagement model is deliberate: | **Customer** | Coulomb (`coulomb-loop`) | Defines *what* to improve, *which repos*, *at what cadence*, and *acceptance criteria* | | **Supplier** | `kaizen-agentic` | Provides agents, CLI tooling, memory/metrics conventions, and engagement playbooks | | **Scheduler** | `activity-core` | Fires cron/event triggers, resolves fleet roster, creates tasks | -| **Roster** | `state-hub` | Canonical repo list, `host_paths`, workstreams, progress events | +| **Roster** | `state-hub` | Canonical repo list, `host_paths`, workplans, progress events | | **Registry** | `reuse-surface` | Capability maturity and registry hygiene signals | Agents are **not Coulomb employees**. They are supplier-provided personas that @@ -49,7 +49,7 @@ engagement starts faster. ## The Four Loops -This engagement establishes four coordinated workstreams: +This engagement establishes four coordinated workplans: | Workplan | Loop | Primary agents | Target | |----------|------|----------------|--------| @@ -143,7 +143,7 @@ requires materially less setup than this one. 1. Three first-order loops run end-to-end on ≥3 pilot repos with activity-core task creation and successful `schedule prepare` sessions. 2. Loop regulator (LOOP-WP-0004) produces weekly health summaries and has demoted or promoted cadence at least once based on evidence. 3. Supplier playbook draft exists in `kaizen-agentic` citing `coulomb-loop` as reference engagement. -4. `coulomb-loop` registered in state-hub with workstreams synced from `workplans/`. +4. `coulomb-loop` registered in state-hub with workplans synced from `workplans/`. ## Related Documents diff --git a/SCOPE.md b/SCOPE.md index b08757c..358f7f9 100644 --- a/SCOPE.md +++ b/SCOPE.md @@ -15,7 +15,7 @@ with project-scoped memory and metrics. - Engagement INTENT, workplans (LOOP-WP-*), ADRs, decision proposals - Loop rosters, cadence state, health records under `loops/` - ActivityDefinition copies for activity-core sync -- state-hub workstream and progress event coordination +- state-hub workplan and progress event coordination - History and assessment artefacts - reuse-surface capability registration for the engagement itself