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

Align operational handoff instructions
All checks were successful
ci / validate (push) Successful in 44s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a0233b-178d-7162-b92f-31a31ea8ca9b
This commit is contained in:
tegwick 2026-08-23 11:53:24 +02:00
parent ef245000b9
commit 3aabd07347
3 changed files with 56 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

7
AGENTS.md
View file

@ -21,11 +21,12 @@ pip install -e . -e ../sand-boxer -e '../rein-aharness[llm]' -e ../rein-openweig
# Test
python3 -m pytest tests/ -q
# Validate the executable profile/rein catalog
# Validate the profile/rein catalog and inspect operational readiness
glas-harness profiles
# Run — resolves the selected constellation, executes, verifies, and tears down
glas-harness run --harness-profile harness.agent-dev-local@1.0.0 \
# Run a bounded proof through an explicit profile. The committed remote profile
# is currently unverified; blocked profiles refuse before sandbox creation.
glas-harness run --harness-profile harness.agent-dev@1.0.0 \
--repo <path> --title "..." --description "..."
```

3
WORK-RECORDS.md
View file

@ -17,6 +17,7 @@
| workplan | GLAS-WP-0006 | finished | — | workplans/GLAS-WP-0006-consumer-actor-validation.md |
| workplan | GLAS-WP-0007 | finished | — | workplans/GLAS-WP-0007-capability-scope-truth.md |
| workplan | GLAS-WP-0008 | finished | — | workplans/GLAS-WP-0008-profile-operational-readiness.md |
| workplan | GLAS-WP-0009 | finished | — | workplans/GLAS-WP-0009-operational-handoff-truth.md |
| task | GLAS-0001-T01 | done | — | workplans/GLAS-0001-statehub-bootstrap.md |
| task | GLAS-0001-T02 | done | — | workplans/GLAS-0001-statehub-bootstrap.md |
| task | GLAS-0001-T03 | done | — | workplans/GLAS-0001-statehub-bootstrap.md |
@ -53,6 +54,8 @@
| task | GLAS-WP-0008-T01 | done | — | workplans/GLAS-WP-0008-profile-operational-readiness.md |
| task | GLAS-WP-0008-T02 | done | — | workplans/GLAS-WP-0008-profile-operational-readiness.md |
| task | GLAS-WP-0008-T03 | done | — | workplans/GLAS-WP-0008-profile-operational-readiness.md |
| task | GLAS-WP-0009-T01 | done | — | workplans/GLAS-WP-0009-operational-handoff-truth.md |
| task | GLAS-WP-0009-T02 | done | — | workplans/GLAS-WP-0009-operational-handoff-truth.md |
| intake | GLAS-IN-0001 | done | blue | docs/intakes/residuals.md |
| intake | GLAS-IN-0002 | todo | red | docs/intakes/residuals.md |
| intake | GLAS-IN-0003 | todo | green | docs/intakes/residuals.md |

49
workplans/GLAS-WP-0009-operational-handoff-truth.md Normal file
View file

@ -0,0 +1,49 @@
---
id: GLAS-WP-0009
type: workplan
title: "Align operator instructions and route residual owners"
domain: infotech
repo: glas-harness
status: finished
owner: codex
topic_slug: operational-handoff-truth
created: "2026-08-23"
updated: "2026-08-23"
---
# Align operator instructions and route residual owners
## Correct the developer workflow
```task
id: GLAS-WP-0009-T01
status: done
priority: high
```
Remove the stale implication that catalog validation proves executable runtime
readiness. Make the example invocation agree with the declared profile states
without claiming an unverified profile is production-ready.
**Completed 2026-08-23:** the developer workflow now calls `profiles` a
catalog/readiness validation command and uses the remote profile only as an
explicitly unverified bounded-proof example. It warns that blocked profiles
refuse before sandbox creation.
## Route remaining owner handoffs
```task
id: GLAS-WP-0009-T02
status: done
priority: medium
```
Route `GLAS-IN-0002` to sand-boxer and `GLAS-IN-0003/0004` to repo-manager with
current evidence and exact acceptance criteria. Preserve these as live
residuals; do not duplicate them or claim externally owned work complete.
**Completed 2026-08-23:** State Hub records for `GLAS-IN-0002/0003/0004` are
now `routed` with exact owner and acceptance notes. Sand-boxer received message
`5b7f8fae-e0e6-4e59-b594-3f6b5a672581`; repo-manager received message
`2e4cbcef-e52d-4bca-9480-2f5f40016d1a`. These three intakes remain live until
their owners promote and complete them; no new residual was created.