the-custodian/docs/attended-window/2026-10-11-daily-red-batch.md

Daily red-lane batch — 2026-10-11

One package for founder disposition; no per-item approval request has been sent. This package contains the new publication item prepared during the renewed critical-path run. It does not replace existing decisions or orange-window acts.

PNEX-WP-0006 — publish build-mode authorization

Publish the accepted Custodian build-mode change rule as a Policy Nexus page and its canon-derived JSON artifact:

• /standards/build-mode-change-authorization/v0.1/
• /guardrails/build-mode-change-authorization.json

Prepared implementation: policy-nexus/tools/guardrails.py, publication entry, expiry header and digest-bound release verification. Sixty tests pass. Local build renders 74 documents and the JSON equals the canonical YAML block. Native publication has not run; both tasks remain waiting.

Review diff: /tmp/pnex6/reviewed.patch; validation: policy-nexus/docs/evidence/2026-10-11-build-mode-guardrail/validation.json. Canon SHA-256: 7135ad8e36041f6dc9633c029109b4751be275f912cec44fc462c9f55befaab8. Artifact SHA-256: a86462a57bb1df5804d3088881af22569082d43ff68bcab2b67cbe56b6fc46cd.

Abort owner: policy-nexus. Before execution, bind the release image and exact source commit, review the resulting native diff, and retain the prior deployment revision. Rollback restores that image/revision and retains immutable publication paths. Verify the live expiry, JSON equality, artifact digest and installed source revision. No new spend ceiling or credential/access scope is proposed.

Release remains blocked independently by an unreviewed net-kingdom/canon/standards/security-layer-model_v0.9.md source-inventory entry. The source owner must resolve its publication disposition before the full audit passes; batch acceptance cannot bypass that release check.

FLEX-WP-0036-T05 — renamed TokenReview principals

The prepared source creates nine ServiceAccounts in access-engine, each with its own identically named -tokenreviewer ClusterRole/ClusterRoleBinding. The only permission is cluster-scoped create on authentication.k8s.io/tokenreviews. Subjects:

• access-engine-application-readback
• access-engine-informed-decision-lifecycle
• access-engine-informed-decision-sitting
• access-engine-informed-decision-t03
• access-engine-ops-warden-fetch
• access-engine-ops-warden
• access-engine-secrets-engine
• access-engine-tenant-engine
• access-engine-user-engine

This adds principals even though capability sets match the existing reviewers, so it requires an exact access-scope disposition. Source preparation is tested; no grant or rollout has run. Receipt: access-engine/docs/evidence/2026-10-11-runtime-twins/access-runtime-twins-prepared-receipt-v2.json. The original blue classification is retained as superseded. Scaling Deployments to zero does not revoke RBAC: recovery also removes only these newly issued bindings. Existing reviewers and consumer grants remain available during recovery. Live execution still requires T03/T04 and the ordered predecessor proof, fresh image/inventory reconciliation, server dry-run, headroom and the reviewed receipt.

The same exact batch includes the proposed runtime naming table in access-engine/decisions/decisions.md (FLEX-DEC-2026-021): namespace/chart access-engine, the nine access-engine-<pin> names, exact DNS origins and caller audience access-engine. This records the intended side-by-side rename; the accepted binary ruling remains FLEX-DEC-2026-020. No broader-table founder acceptance is inferred from the binary ruling. Protected consumer bindings and grants retain their original meanings.

FLEX-WP-0036-T04 — new public image package

Publish the exact reviewed Access Engine source under forgejo.coulomb.social/coulomb/access-engine, retaining the existing coulomb/flex-auth package through the migration. tools/publish-runtime-images.sh builds once, tags both names, then independently pulls each published immutable tag and checks equal registry manifest digests, including OCI indexes and attestations. A local image/config digest alone cannot satisfy the gate.

Normal push CI continues to publish only the already admitted legacy package. Paired publication is an explicit workflow_dispatch with publish_runtime_rename: true, after the batch disposition and binding to the exact committed source revision. No paired dispatch or new-package publication has run. Local image build, renamed entrypoint, both policy paths and the exit-2 legacy stub are verified. The lifecycle Containerfile's stale stub entrypoint is repaired. Abort owner: access-engine. Stop on a failed push, pull or digest mismatch; retain the partial publication record and do not switch any workload. Recovery retains existing workload pins and prior published digests; no registry deletion is proposed. New reviewer grants and runtime deployment remain separate verified steps after their exact approval.