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

fix: use canonical harness workplan prefix

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a02b6f-7db1-7222-918b-e813a6bda38d
This commit is contained in:
tegwick 2026-08-23 11:32:24 +02:00
parent 9afacdbfba
commit 7b0b541113
3 changed files with 27 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

17
AGENTS.md
View file

@ -7,7 +7,12 @@
**Domain:** infotech
**Repo slug:** rein-aharness
**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
**Workplan prefix:** `REIN-A-`
**Workplan prefix:** `HARNESS-WP-`
`REIN-A-0001` through `REIN-A-0004` are immutable historical identifiers from
before the fleet `PREFIX-WP-NNNN` convention. Preserve them in references and
archives, but use the registered `HARNESS-WP-` prefix for every new workplan
and task.
---
@ -142,10 +147,10 @@ curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
Work items originate as files in this repo — not in the hub. The hub is a
read/cache/index layer that rebuilds from files.
**File location:** `workplans/REIN-A-NNNN-<slug>.md`
**File location:** `workplans/HARNESS-WP-NNNN-<slug>.md`
**Archived location:** finished workplans may move to
`workplans/archived/YYMMDD-REIN-A-NNNN-<slug>.md`. The `YYMMDD` prefix is
`workplans/archived/YYMMDD-HARNESS-WP-NNNN-<slug>.md`. The `YYMMDD` prefix is
the completion/archive date; the frontmatter `id` does not change.
**Ad Hoc Tasks:** small opportunistic fixes discovered during a session use
@ -157,7 +162,7 @@ anything needing analysis, design, approval, dependencies, or multiple phases.
```yaml
---
id: REIN-A-NNNN
id: HARNESS-WP-NNNN
type: workplan
title: "..."
domain: infotech
@ -185,7 +190,7 @@ API/MCP/frontmatter bridges until `STATE-WP-0069` retires them — see
## Task Title
` ` `task
id: REIN-A-NNNN-T01
id: HARNESS-WP-NNNN-T01
status: wait | todo | progress | done | cancel
priority: high | medium | low
state_hub_task_id: "<uuid>" # written by fix-consistency — do not edit
@ -198,7 +203,7 @@ Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blo
**Residuals when finishing:** actionable leftovers become live work records
before `status: finished` — usually an intake (`origin: residual`,
`origin_ref: REIN-A-NNNN`) or a spawned workplan. Residual is a *role*,
`origin_ref: HARNESS-WP-NNNN`) or a spawned workplan. Residual is a *role*,
not a kind. Fleet list lives on State Hub, not in `SCOPE.md`.
To create a new workplan: