coulomb/issue-core
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 1s
Details

Browse source
This commit is contained in:
tegwick 2026-07-08 16:41:19 +02:00
parent 882ccd11aa
commit f4195b8c63
4 changed files with 4 additions and 4 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

@ -111,6 +111,6 @@ issue-core is intentionally narrow. The following live elsewhere:
- `SCOPE.md` — concrete in/out-of-scope decisions and integration boundaries. - `SCOPE.md` — concrete in/out-of-scope decisions and integration boundaries.
- `ROADMAP.md` — feature trajectory. - `ROADMAP.md` — feature trajectory.
- `workplans/` — active workstreams. - `workplans/` — active workplans.
- activity-core `docs/adr/adr-001-event-bridge-architecture.md` — the IssueSink - activity-core `docs/adr/adr-001-event-bridge-architecture.md` — the IssueSink
contract that issue-core honors at `POST /issues/`. contract that issue-core honors at `POST /issues/`.

2
SCOPE.md
View file

@ -165,6 +165,6 @@ mutate it.
- `INTENT.md` — why issue-core exists and how it fits in the Coulomb org. - `INTENT.md` — why issue-core exists and how it fits in the Coulomb org.
- `ROADMAP.md` — feature trajectory. - `ROADMAP.md` — feature trajectory.
- `workplans/ISSC-WP-0001-rename-and-task-ingestion.md` — current rename + - `workplans/ISSC-WP-0001-rename-and-task-ingestion.md` — current rename +
ingestion workstream. ingestion workplan.
- activity-core `docs/adr/adr-001-event-bridge-architecture.md` — the upstream - activity-core `docs/adr/adr-001-event-bridge-architecture.md` — the upstream
side of the IssueSink contract. side of the IssueSink contract.

2
workplans/ISSC-WP-0001-rename-and-task-ingestion.md
View file

@ -59,7 +59,7 @@ in the Coulomb org architecture:
Handles task creation and tracking. Has no incoming task-ingestion API from Handles task creation and tracking. Has no incoming task-ingestion API from
external callers like activity-core. external callers like activity-core.
- **State hub gap**: issue-facade is not registered in the Custodian State Hub. - **State hub gap**: issue-facade is not registered in the Custodian State Hub.
This makes cross-repo workstream tracking impossible. This makes cross-repo workplan tracking impossible.
See: `docs/adr/adr-001-event-bridge-architecture.md` in activity-core for the See: `docs/adr/adr-001-event-bridge-architecture.md` in activity-core for the
IssueSink adapter design and the task emission flow. IssueSink adapter design and the task emission flow.