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

Record deployed queue boundary

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 13:08:51 +02:00
parent 74d7801b22
commit 36e10962f7
2 changed files with 29 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

9
workplans/HARNESS-WP-0003-governed-runtime-integrity.md
View file

@ -126,6 +126,15 @@ and T02–T06 can cite stable decisions rather than infer ownership from code.
(`704aa396-52b7-4c9f-80b7-6cf8a81ce0a1`). Glas reconfirmed the exact
revision and digest in `9638537b-e3c3-414d-a2d7-8beab61a4e1f`; revised
Activity Core, sand-boxer, and llm-connect acknowledgements remain pending.
- Activity Core message `900801f4-0641-4e87-90e6-0279b6c892a6` reports the
requested boundary deployed under `ACTIVITY-WP-0036` at revisions `f0a897e`
and `3cd5250`: the worker token is bound to configured
`rein-aharness@railiance01`, mismatched body and operator/SSO identities are
rejected, and heartbeat/complete/fail enforce row-locked active leases with
equal-to-expiry treated as expired. Its 468-test suite and live spoof refusal
passed. ADR-002 now records this as deployed current state; natural
heartbeat/late-close production evidence remains pending for the next real
claimed row rather than a manufactured run.
## Make each repository run a lease-bound transaction