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

Enforce bounded operation guardrails
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
Details
Build and Publish Container Image / build-and-push (push) Successful in 21s
Details

Browse source 
Assistant: codex
Assistant-Model: gpt-5.6-sol
Assistant-Session: 01a028de-e2c8-7732-8521-46a7fc5db82f
This commit is contained in:
tegwick 2026-08-23 12:31:13 +02:00
parent c384f60530
commit 26934e25b9
51 changed files with 1843 additions and 472 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/execution-queue-boundary.md
View file

@ -39,6 +39,10 @@ ops_run being `open` is an **automation fire**. Those are different planes
(ACT-ADR-005). Mapping State Hub `POST /execution/launch-requests` onto
“create a workplan execution row here” would collapse them again.
The bounded-operation registry in ACT-ADR-007 is a separate, code-reviewed
maintenance exception. It neither consumes this queue nor turns an `ops_run`
into a workplan task.
## Replacement for State Hub routes
| State Hub route | Replacement |