feat: route Custodian routines through bounded owner operations
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 1s
Build and Publish Container Image / build-and-push (push) Successful in 2m22s

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
This commit is contained in:
tegwick 2026-10-19 13:53:00 +02:00
parent 7490eb8004
commit 4ae00fcd23
13 changed files with 578 additions and 175 deletions

View file

@ -368,3 +368,16 @@ Unstaged source edits are preserved; unstaged generated-file edits and unresolve
conflicts stop the commit. The existing generated-only guard and secret scan
remain in place. This adoption covers WORK-RECORDS.md only; other owner indexes
retain their own generators. It makes no schedule or public-release change.
## Custodian deterministic operations
The existing bounded-operation stage registers custodian_security_flow and
custodian_allocation_review: fixed owner commands with trusted operator-bound
source/fleet/private-state inputs, explicit definition parameters, timeout
containment and compact counted/hash receipts. Both definitions remain disabled.
No coding-agent task or green-commit profile executes these routines. Runtime
placement, accepted mounts/network, delivery and first unattended proof remain
unverified; see docs/custodian-bounded-operations.md. This adds no scheduler or
generic shell. The generated .custodian-brief.md is now an ignored local
orientation snapshot; its existing bytes remain local.