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

Complete KG-WP-0004-T04: propose containment, do not actuate

Browse source 
Response ladder, authority grant, effector example, and Phase 5 now
separate Staff proposals from Engine/PEP execution. Actuation stays
unowned. Origin linkage matches WP-0003-T06.

Assistant: grok
Assistant-Session: 01a05ef1-9e5a-70f2-b0ff-0b05d6b38ae9
This commit is contained in:
tegwick 2026-09-02 08:11:34 +02:00
parent ac69d96f4e
commit ac3aa1287e
3 changed files with 169 additions and 107 deletions
Download patch file Download diff file Expand all files Collapse all files

9
workplans/KG-WP-0004-architecture-layer-vocabulary-sweep.md
View file

@ -179,7 +179,7 @@ the same way. Head note still cites v0.6 / KG-IN-0002 — that rewrite is T05.
```task
id: KG-WP-0004-T04
status: todo
status: done
priority: high
state_hub_task_id: "bbb4c1aa-2808-5fde-8f9b-7fb7730f13c7"
```
@ -205,6 +205,13 @@ Done when:
- Phase 5 cannot be read as "kings-guard will automatically contain";
- the effector example is a proposal, reconstructable to its origin.
**Done 2026-09-02:** §9.7 ladder is propose vs execute; safety envelope is
PEP/actuation. §16 grant is no longer issued to a Staff node. §25.2
`effector_request` carries origin observation/signal, `advisory_only`, and
`request_containment`. Phase 5 is bounded proposal; success is
reconstructability, not automatic containment. Fast local loop named as PEP
(qonto-assistant). AD-003/AD-005 and §35/§36 match propose-not-act.
## Task: Prove no Staff decision point; refresh the layer note
```task