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

Adopt canonical HARNESS-WP prefix, add State Hub bootstrap files

Browse source 
Registered with State Hub (statehub register) and renamed
REIN-A-WP-0002 to HARNESS-WP-0002 per fix-consistency's C-26 check
(repo's canonical workplan prefix is HARNESS-WP, established by
HARNESS-WP-0001).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-26 12:32:59 +02:00
parent 61d8a39802
commit 9cd95c531a
6 changed files with 323 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

6
.gitignore vendored
View file

@ -163,3 +163,9 @@ cython_debug/
#.idea/ #.idea/
llm_connect_vendor/ llm_connect_vendor/
# state-hub: track .claude/rules
# Claude Code local state (track shared rules; ignore machine-specific files)
.claude/*
!.claude/rules/
!.claude/rules/*.md

189
AGENTS.md Normal file
View file

@ -0,0 +1,189 @@
# rein-aharness — Agent Instructions
## Repo Identity
**Purpose:** Claude-Code-CLI-driven rein: governed, unattended/scheduled agent runtime
**Domain:** infotech
**Repo slug:** rein-aharness
**Topic ID:** `cee7bedf-2b48-46ef-8601-006474f2ad7a`
**Workplan prefix:** `REIN-A-`
---
## State Hub Integration
The Custodian State Hub tracks work across all domains. Interact via HTTP REST —
there is no MCP server for Codex agents.
| Context | URL |
|---------|-----|
| Local workstation | `http://127.0.0.1:8000` |
| Remote via tunnel | `http://127.0.0.1:18000` |
| Optional local edge relay | http://127.0.0.1:18080 |
When an operator has enabled the edge relay, set API_BASE to the relay URL.
Queueable writes return an explicit queued receipt if the central hub is
unreachable. Treat that as pending local evidence, then ask the operator to run
statehub outbox status/replay after connectivity returns.
### Orient at session start
```bash
# Offline brief — works without hub connection
cat .custodian-brief.md
# Active workplans for this domain
curl -s "http://127.0.0.1:8000/workplans/?topic_id=cee7bedf-2b48-46ef-8601-006474f2ad7a&status=active" \
| python3 -m json.tool
# Check inbox
curl -s "http://127.0.0.1:8000/messages/?to_agent=rein-aharness&unread_only=true" \
| python3 -m json.tool
```
Mark a message read:
```bash
curl -s -X PATCH "http://127.0.0.1:8000/messages/<id>/read" \
-H "Content-Type: application/json" -d '{}'
```
### Log progress (required at session close)
```bash
curl -s -X POST http://127.0.0.1:8000/progress/ \
-H "Content-Type: application/json" \
-d '{
"summary": "what was done",
"event_type": "note",
"author": "codex",
"workplan_id": "<uuid>",
"task_id": "<uuid>"
}'
```
Omit `workplan_id` / `task_id` when not applicable.
### Update task status
```bash
curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
-H "Content-Type: application/json" \
-d '{"status": "progress"}'
# values: wait | todo | progress | done | cancel
```
### Flag a task for human review
```bash
curl -s -X PATCH "http://127.0.0.1:8000/tasks/<task_id>" \
-H "Content-Type: application/json" \
-d '{"needs_human": true, "intervention_note": "reason"}'
```
---
## Session Protocol
**Start:**
1. `cat .custodian-brief.md` — domain goal and open workplans (offline-safe)
2. Check inbox: `GET /messages/?to_agent=rein-aharness&unread_only=true`; mark read
3. Scan workplans: `ls workplans/` — note `status: ready`, `active`, or `blocked` files and open tasks
4. Check human-needed tasks: `GET /tasks/?needs_human=true`
**During work:**
- Update task statuses in workplan files as tasks progress
- Record significant decisions via `POST /decisions/`
**Close:**
1. Update workplan file task statuses to reflect progress
2. If finishing a workplan: hand off **residuals** as live work records first
(intake with `origin: residual` + `origin_ref: <WP-id>`, or a next workplan /
decision / engagement). Do not park leftovers only in prose or `SCOPE.md`.
Canon: `the-custodian/canon/standards/work-record-types_v0.1.md` § Residuals.
3. Log: `POST /progress/` with a summary of what changed (name handoff ids)
4. After workplan file changes, run:
```bash
statehub fix-consistency
```
Coding agents should run this directly; ask the operator only if the CLI or
State Hub API is unavailable. This syncs task status from files into the hub DB.
---
{CREDENTIAL_ROUTING}
<!-- REPO-AGENTS-EXTENSIONS -->
<!-- Append repo-specific agent instructions below this marker.
The state-hub template sync preserves content after this line. -->
---
## Workplan Convention (ADR-001)
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`
**Archived location:** finished workplans may move to
`workplans/archived/YYMMDD-REIN-A-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
`workplans/ADHOC-YYYY-MM-DD.md` with task ids `ADHOC-YYYY-MM-DD-T01`, etc. Use
this only for low-risk work completed directly; create a normal workplan for
anything needing analysis, design, approval, dependencies, or multiple phases.
**Frontmatter:**
```yaml
---
id: REIN-A-NNNN
type: workplan
title: "..."
domain: infotech
repo: rein-aharness
status: proposed | ready | active | blocked | backlog | finished | archived
owner: codex
topic_slug: ...
created: "YYYY-MM-DD"
updated: "YYYY-MM-DD"
state_hub_workstream_id: "<uuid>" # fix-consistency — do not edit (legacy field name; workplan UUID)
---
```
Use `proposed` for a new draft, `ready` after review against current repo
state, and `finished` after implementation. `stalled` and `needs_review` are
derived health labels, not frontmatter statuses.
**Terminology:** workplan is the fleet term; `workstream` appears only in legacy
API/MCP/frontmatter bridges until `STATE-WP-0069` retires them — see
`the-custodian/canon/standards/workplan-terminology-fleet_v0.1.md`.
**Task block format** (one per `##` section):
```
## Task Title
` ` `task
id: REIN-A-NNNN-T01
status: wait | todo | progress | done | cancel
priority: high | medium | low
state_hub_task_id: "<uuid>" # written by fix-consistency — do not edit
` ` `
Task description text.
```
Status progression: `todo` → `progress` → `done`; use `wait` for waiting/blocked work and `cancel` for stopped work.
**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*,
not a kind. Fleet list lives on State Hub, not in `SCOPE.md`.
To create a new workplan:
1. Write the file following the format above
2. Run `statehub fix-consistency` locally; ask the operator only if the CLI or
State Hub API is unavailable.

32
SCOPE.md Normal file
View file

@ -0,0 +1,32 @@
# SCOPE
> This file was generated by `statehub register`. Refine it as the repository
> boundaries become clearer.
## One-liner
Claude-Code-CLI-driven rein: governed, unattended/scheduled agent runtime
## Core Idea
rein-aharness exists to provide the capability described in INTENT.md.
## In Scope
- Maintain the repository's primary implementation.
- Keep docs, tests, and operational metadata current.
## Out of Scope
- Own unrelated adjacent systems.
- Make irreversible operational decisions without human approval.
## Current State
- Status: active; implementation and stability should be verified by the repo agent.
## Getting Oriented
- Start with: INTENT.md
- Agent instructions: AGENTS.md
- Workplans: workplans/

27
WORK-RECORDS.md Normal file
View file

@ -0,0 +1,27 @@
# Work Records — rein-aharness
> Generated by `statehub fix-consistency` (CUST-WP-0061-T04, work-record
> stage 3). Do not edit by hand — edit the source file/block listed for
> each record and re-run fix-consistency to refresh this index. Archived
> workplans are omitted; closed decisions/intakes/engagements stay listed
> so recently-resolved work is still visible. [auto]
| Kind | ID | Status | Lane | Source |
| --- | --- | --- | --- | --- |
| workplan | HARNESS-WP-0001 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| workplan | REIN-A-0001 | ready | — | workplans/REIN-A-0001-statehub-bootstrap.md |
| workplan | REIN-A-WP-0002 | proposed | — | workplans/REIN-A-WP-0002-rename-and-glas-harness-alignment.md |
| task | HARNESS-WP-0001-T01 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | HARNESS-WP-0001-T02 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | HARNESS-WP-0001-T03 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | HARNESS-WP-0001-T04 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | HARNESS-WP-0001-T05 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | HARNESS-WP-0001-T06 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | HARNESS-WP-0001-T07 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | REIN-A-0001-T01 | todo | — | workplans/REIN-A-0001-statehub-bootstrap.md |
| task | REIN-A-0001-T02 | todo | — | workplans/REIN-A-0001-statehub-bootstrap.md |
| task | REIN-A-0001-T03 | todo | — | workplans/REIN-A-0001-statehub-bootstrap.md |
| task | REIN-A-WP-0002-T01 | done | — | workplans/REIN-A-WP-0002-rename-and-glas-harness-alignment.md |
| task | REIN-A-WP-0002-T02 | todo | — | workplans/REIN-A-WP-0002-rename-and-glas-harness-alignment.md |
| task | REIN-A-WP-0002-T03 | todo | — | workplans/REIN-A-WP-0002-rename-and-glas-harness-alignment.md |
| task | REIN-A-WP-0002-T04 | todo | — | workplans/REIN-A-WP-0002-rename-and-glas-harness-alignment.md |

15
workplans/REIN-A-WP-0002-rename-and-glas-harness-alignment.md → workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md
View file

@ -1,7 +1,8 @@
--- ---
id: REIN-A-WP-0002 id: HARNESS-WP-0002
title: "Rename completion and glas-harness alignment" title: "Rename completion and glas-harness alignment"
status: proposed status: proposed
state_hub_workstream_id: "c53fe489-845b-42b3-8e7f-c7e4e6f16b25"
--- ---
Follow-up to HARNESS-WP-0001 (done) and glas-harness Follow-up to HARNESS-WP-0001 (done) and glas-harness
@ -22,9 +23,10 @@ touch the CLI command name, Python package name, or deploy artifacts —
see next task. see next task.
```task ```task
id: REIN-A-WP-0002-T01 id: HARNESS-WP-0002-T01
status: done status: done
priority: high priority: high
state_hub_task_id: "bf04ed50-cbe2-4f8f-9876-d06c579d19e6"
``` ```
## Task: Deploy/package rename (deliberate follow-up, needs a maintenance window) ## Task: Deploy/package rename (deliberate follow-up, needs a maintenance window)
@ -42,9 +44,10 @@ reviewed change with a Railiance re-deploy and smoke-test run
immediately after, not as incidental cleanup. immediately after, not as incidental cleanup.
```task ```task
id: REIN-A-WP-0002-T02 id: HARNESS-WP-0002-T02
status: todo status: todo
priority: medium priority: medium
state_hub_task_id: "7c5d23cd-d7fd-4c79-8847-448b83feb673"
``` ```
## Task: Implement the glas-harness rein contract ## Task: Implement the glas-harness rein contract
@ -56,9 +59,10 @@ into `rein-aharness` instead of `rein-aharness` only running itself via
its own CLI/poll loop. its own CLI/poll loop.
```task ```task
id: REIN-A-WP-0002-T03 id: HARNESS-WP-0002-T03
status: todo status: todo
priority: high priority: high
state_hub_task_id: "228e999c-807b-4456-a286-4e3ab4fc8e90"
``` ```
## Task: Decide scheduling/blueprint coupling boundary ## Task: Decide scheduling/blueprint coupling boundary
@ -72,7 +76,8 @@ Record the answer in `glas-harness/docs/adr/` before T03 forces the
question implicitly. question implicitly.
```task ```task
id: REIN-A-WP-0002-T04 id: HARNESS-WP-0002-T04
status: todo status: todo
priority: low priority: low
state_hub_task_id: "31e2b763-8f04-4523-bd2b-ce4506b55700"
``` ```

59
workplans/REIN-A-0001-statehub-bootstrap.md Normal file
View file

@ -0,0 +1,59 @@
---
id: REIN-A-0001
type: workplan
title: "Bootstrap State Hub integration"
domain: infotech
repo: rein-aharness
status: ready
owner: codex
topic_slug: custodian
created: "2026-07-26"
updated: "2026-07-26"
state_hub_workstream_id: "e10231e6-a051-43dd-8343-b3963d25cbaa"
---
# Bootstrap State Hub integration
Claude-Code-CLI-driven rein: governed, unattended/scheduled agent runtime
## Review Generated Integration Files
```task
id: REIN-A-0001-T01
status: todo
priority: high
state_hub_task_id: "69710723-4fc0-4b64-953d-166520167493"
```
Review `INTENT.md`, `SCOPE.md`, `AGENTS.md`, and `.custodian-brief.md`.
Replace generated placeholders with repo-specific facts where needed.
## Verify Local Developer Workflow
```task
id: REIN-A-0001-T02
status: todo
priority: high
state_hub_task_id: "8a060f11-b5d7-4d99-b740-db102342249a"
```
Identify the repo's install, test, lint, build, and run commands. Add or refine
those commands in the agent instructions so future coding sessions can verify
changes confidently.
## Seed First Real Workplan
```task
id: REIN-A-0001-T03
status: todo
priority: medium
state_hub_task_id: "ee1b1a63-89e1-4743-8ec2-c0ce9b2b44d5"
```
Create the first implementation workplan for the repository's most important
next change. After workplan file updates, run the sync locally from this repo
checkout:
```bash
statehub fix-consistency
```