feat: prepare pinned Custodian worker bundle and required input admission

Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
This commit is contained in:
tegwick 2026-10-19 15:09:27 +02:00
parent 0319fe8be8
commit fed119a17c
18 changed files with 1058 additions and 2 deletions

View file

@ -74,3 +74,11 @@ dispatch. It never invokes the real security command, Hub or schedule activation
Concrete delivery options and unresolved owner choices are recorded in
[custodian-runtime-binding-proposal.md](custodian-runtime-binding-proposal.md).
Daily execution requires `ACTIVITY_CORE_CUSTODIAN_INPUT_POLICY` and `ACTIVITY_CORE_CUSTODIAN_FRESHNESS_RECEIPTS`, a protected JSON array of
existing Repo Manager receipts. Admission verifies exact complete snapshot
contents and fresh per-repo Forge observations before starting subprocesses.
The existing-worker candidate configures this gate; missing policy or receipts
refuse execution before subprocess. Native freshness noops rely on protected
Repo Manager issuer custody: the issuer checks HEAD against its last successful
commit before emitting `forge_head_matches_last_success`.

View file

@ -1,5 +1,11 @@
# Custodian runtime binding proposal
Update: user selected the existing worker. The concrete pinned image package,
private state/fleet mount candidate and tunable policy now live in
[`k8s/custodian-release/README.md`](../k8s/custodian-release/README.md).
That packet supersedes the placement alternatives below. It remains outside
active kustomization; schedules are disabled.
Review artifact, 2026-10-19. Not a deployment or activation approval. Both native
ActivityDefinitions remain `enabled: false`. No manifests, images or schedules
were changed for this proposal. Read with `custodian-bounded-operations.md`.