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

Plan intent boundary guardrails
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
Details
CI Smoke / container-smoke (push) Successful in 1s
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 11:24:58 +02:00
parent 6aa06c3e24
commit c384f60530
2 changed files with 318 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

14
history/2026-08-23-scope-against-intent-assessment.md
View file

@ -235,3 +235,17 @@ operations around that bridge. Those additions are useful and controlled, but
INTENT must name them precisely so future contributors can distinguish accepted
operational state from prohibited task lifecycle and accepted bounded actions
from a general executor.
## Follow-up workplan
`ACTIVITY-WP-0035` addresses the locally actionable and boundary-defining gaps:
- G1 operational delivery state vs work-item lifecycle;
- G2 bounded-operation admission and workflow separation;
- G6 truthful review-worthy output semantics;
- G7 bounded instruction audit promises; and
- G8 misleading compatibility surfaces.
G3 remains with ACTIVITY-WP-0031, G4 with ACTIVITY-WP-0032, G5 with the State
Hub retirement program after ACTIVITY-WP-0029's completed port slice, and G9
with ACTIVITY-WP-0034's natural-run acceptance gate.