coulomb/informed-decision
5
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
informed-decision/docs/batches/2026-10-04-state-hub-wp0094/OPERATOR.md
tegwick bb6198407e Prepare the STATE-WP-0094 production-steps sitting (four memos, unposted) 
Hub decision 7b19de6c-72a1-409e-89a9-ec3ac09c03fd stays pending; the batch
never resolves it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 692292@bnt-lap001
Assistant-Session: 89c7d8e8-e1b3-47eb-9411-a0ab227fca2f
2026-10-04 13:24:34 +02:00

2.9 KiB
Raw Blame History

STATE-WP-0094 production steps — operator packet

Hub decision: 7b19de6c-72a1-409e-89a9-ec3ac09c03fd (pending). The founder answers through informed-decision. This packet never resolves that decision (resolves: never). Review group: net-kingdom-admins. Surface, after the steps below: https://decisions.coulomb.social/

An agent prepared this sitting. It may not accept, decline, or seal. Only the human binds. Each memo is one question; approve-all is forbidden.

# Memo Question Required acknowledgement
1 state-hub-edge-receiving-rollout-c287ed8 Deploy State Hub c287ed8 to railiance01? deploy-only
2 owner-return-pickup-plan-b2c6c56 Approve owner-return pickup plan, definition, grant and one gated trial? preconditions-open
3 freshness-runner-deploy-trial-e77f8b4 Deploy the freshness runner and run up to three --limit 3 trials? no-schedule
4 freshness-schedule-enable-retire-sweep Enable the freshness schedule and retire the legacy sweep? after-clean-trials

Packet hashes are in provisioning/index.json (sha256 of each .packet.md). Order matters: 2 and 4 depend on 1 and 3 being carried out cleanly.

Current state at preparation (2026-10-04): State Hub Helm revision 72, main-5dd3df9. Nothing in this batch has been deployed, scheduled, posted, admitted or loaded.

What you run

  1. Approval Engine tunnel, separate terminal: kubectl -n approval-engine port-forward svc/approval-engine 18281:8080

  2. Create the four native approvals in your own terminal (KeyCape OIDC/MFA opens in the browser). Do not hand this command to an agent.

    WARDEN_ROUTING_CATALOG=/home/worsch/ops-warden/registry/routing/catalog.yaml \
BAO_ADDR=http://127.0.0.1:18200 VAULT_ADDR=http://127.0.0.1:18200 \
warden access informed-decision-sitting-requester-login --exec -- \
  /home/worsch/informed-decision/tools/create_sitting_approvals.sh \
  --sitting 2026-10-04-state-hub-wp0094 \
  --receipt 2026-10-04-state-hub-wp0094-approval-create.json --expect 4

    Read warden's printed line, not its exit code. Do not retry when a receipt was not retained.

  3. Exact-record admission and store load: a new access-engine policy version that admits exactly these four memos, plus the review runtime ConfigMap, following the v9 pattern in ../2026-10-04-emergent-profile/DEPLOY-v9.md. This is its own deploy and needs your separate "yes, deploy it".

  4. Answer each memo at the surface with fresh MFA.

After an answer

Agents act only on an accepted memo, only within its packet, and record the evidence named there. A declined or returned memo stops that step. The hub decision is resolved only once all four memos have an answer.

Must not

  • Paste or display any credential value
  • Let an agent accept, decline, or seal
  • Call POST /v1/memos or resolve the hub decision from this packet
  • Treat approval of one memo as approval of another