coulomb/helix-forge
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 3)
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 3s
Details

Browse source
This commit is contained in:
tegwick 2026-07-08 17:15:46 +02:00
parent 8ed545050e
commit 52b1c40e09
2 changed files with 2 additions and 2 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
`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

2
SCOPE.md
View file

@ -113,7 +113,7 @@ test suite. `INTENT.md` is the main source of truth.
- `inter-hub` - governed interaction substrate that HelixForge may extend.
- `ops-hub` - VSM Operations / System 1 Inter-Hub extension implementation;
local path `/home/worsch/ops-hub`.
- `the-custodian/state-hub` - cross-repo state, workstream, capability, and
- `the-custodian/state-hub` - cross-repo state, workplan, capability, and
progress index.
- `railiance-infra`, `railiance-cluster`, `railiance-platform`,
`railiance-enablement`, `railiance-apps` - operational stack referenced by