coulomb/repo-scoping
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: workplan-first agent guidance prose (CUST-WP-0055 T04 batch 2)
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source
This commit is contained in:
tegwick 2026-07-08 16:41:26 +02:00
parent e145a5a38f
commit 4a2a6cb408
3 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

2
.claude/rules/workplan-convention.md
View file

@ -46,7 +46,7 @@ fix-consistency. Do not edit or rename it.
**Workplan** is the fleet term — see **Workplan** is the fleet term — see
`the-custodian/canon/standards/workplan-terminology-fleet_v0.1.md`. `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 (`workstream_id`), MCP aliases (`create_workstream`), and the frontmatter field
above remain until `STATE-WP-0069` retires them via legacy-meter. Treat those 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 identifiers as workplan IDs. Prefer `GET /workplans/` and `workplan_id` in new

2
INTENT.md
View file

@ -102,7 +102,7 @@ characteristics support those claims.
## How It Fits ## How It Fits
- Upstream coordination: the Custodian State Hub owns workstream/task state, - Upstream coordination: the Custodian State Hub owns workplan/task state,
managed repository records, and capability routing. managed repository records, and capability routing.
- Downstream consumers: Custodian agents and humans use repo-scoping to inspect, - Downstream consumers: Custodian agents and humans use repo-scoping to inspect,
refine, and refresh repository utility profiles. refine, and refresh repository utility profiles.

2
SCOPE.md
View file

@ -102,7 +102,7 @@ characteristics support those claims.
## How It Fits ## How It Fits
- Upstream coordination: the Custodian State Hub owns workstream/task state, - Upstream coordination: the Custodian State Hub owns workplan/task state,
managed repository records, and capability routing. managed repository records, and capability routing.
- Downstream consumers: Custodian agents and humans use repo-scoping to inspect, - Downstream consumers: Custodian agents and humans use repo-scoping to inspect,
refine, and refresh repository utility profiles. refine, and refresh repository utility profiles.