informed-decision/docs/batches/2026-10-04-emergent-profile/OPERATOR.md

Emergent profile adoption — operator packet

Hub decision: d20a9750-2b29-534e-8227-fb866581a6ca. The founder answers through informed-decision. This packet does not resolve that hub decision (resolves: never). Review group: net-kingdom-admins. Surface, after the steps below: https://decisions.coulomb.social/ Memo: emergent-profile-adoption-0-2-6. Question: Accept Emergent Security knowledge 0.2.6 as a non-normative NetKingdom agent orientation profile? Target: emergent-security:knowledge:0.2.6:8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02. Packet hash: sha256:df4a9e0670901aa230d9f33fc9bd2fd1b1f967ef7e2613f840a257cb6b0a1197. Required acknowledgement: acceptance is the orientation boundary of this exact release. It is not runtime permission, and it does not finish independent review, provider continuity, or fleet rollout.

An agent prepared this sitting. It may not accept, decline, or seal. Only the human binds.

The create receipt is docs/evidence/2026-10-04-emergent-profile-approval-create.json. It holds one approval, 05751e09-3a5b-4a41-a4e8-b79e96de6484, binding digest sha256:7843e660694dcd7c806dc02ee0cca05dd3a96488f614b1946291496259a02001, status requested, with no human entry. It expires 2026-10-04T23:52:37Z. The tool labels that phase seven_unapproved_requests_created; the receipt contains this one request.

What you run

1. Approval Engine tunnel, in a separate terminal:

kubectl -n approval-engine port-forward svc/approval-engine 18281:8080

2. Create the native approval, 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-emergent-profile \
  --receipt 2026-10-04-emergent-profile-approval-create.json --expect 1

The child is silent. The outcome is docs/evidence/2026-10-04-emergent-profile-approval-create.json, which holds the approval id and the engine-computed binding digest and no secret. Read warden's printed line, not its exit code.

3. Exact-record admission and store load are done. Policy v9 admits this one memo. The review runtime pin is informed-decision-runtime-35b00b8608e0. See DEPLOY-v9.md.

4. The founder accepted the memo at 2026-10-04T00:16:08Z. The required highlight orientation-only was acknowledged. Approval Engine confirmed the entry. Evidence: docs/evidence/2026-10-04-emergent-profile-acceptance.json.

That acceptance is orientation only. It does not mark EMERGENT-WP-0002 done, close RISK-F-0015, or authorize production use.

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
• Retry approval creation when a receipt was not retained