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

Close HARNESS-WP-0002-T04 per glas-harness ADR-003

Browse source 
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
tegwick 2026-07-26 14:52:01 +02:00
parent a6151c1551
commit a3fc75ced1
2 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
WORK-RECORDS.md
View file

@ -20,7 +20,7 @@
| task | HARNESS-WP-0001-T07 | done | — | workplans/HARNESS-WP-0001-harness-foundation.md |
| task | HARNESS-WP-0002-T01 | done | — | workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md |
| task | HARNESS-WP-0002-T02 | progress | — | workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md |
| task | HARNESS-WP-0002-T03 | progress | — | workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md |
| task | HARNESS-WP-0002-T03 | done | — | workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md |
| task | HARNESS-WP-0002-T04 | todo | — | workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.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 |

18
workplans/HARNESS-WP-0002-rename-and-glas-harness-alignment.md
View file

@ -138,17 +138,19 @@ state_hub_task_id: "228e999c-807b-4456-a286-4e3ab4fc8e90"
## Task: Decide scheduling/blueprint coupling boundary
This repo depends directly on `kaizen-agentic` (blueprints) and
`activity-core`/`issue-core` (task intake). Decide, once
`rein-openweights` exists as a second rein with a possibly different
triggering model, whether that coupling stays rein-local (each rein
sources its own tasks) or moves into glas-harness as a shared concern.
Record the answer in `glas-harness/docs/adr/` before T03 forces the
question implicitly.
Resolved in `glas-harness/docs/adr/ADR-003-scheduling-and-blueprint-sourcing-stay-rein-local.md`:
**stays rein-local.** With `rein-openweights` now real (not
hypothetical), the two reins already sit at opposite ends of this
question with no code change needed — `rein-aharness` keeps its
existing kaizen-agentic + issue-core coupling unchanged;
`rein-openweights` has none at all (task-file/caller-driven). glas-harness
does not become a task source or scheduler, consistent with its own
INTENT.md boundary ("Not a scheduler... activity-core" already listed
under "What it is not").
```task
id: HARNESS-WP-0002-T04
status: todo
status: done
priority: low
state_hub_task_id: "31e2b763-8f04-4523-bd2b-ce4506b55700"
```