Prepare the 0.2.6 profile sitting for the founder.

The dry run posts nothing. The founder creates the approval and answers it.

Assistant: grok
Assistant-Session: 01a10286-9185-7bb2-b411-89cf6ab4c0c6
This commit is contained in:
tegwick 2026-10-04 00:53:46 +02:00
parent 01c46ff454
commit ec1bdad5b8
5 changed files with 198 additions and 0 deletions

View file

@ -0,0 +1,49 @@
# 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 dry run listed this one memo and posted nothing.
## What you run
**1. Approval Engine tunnel**, in a separate terminal:
```bash
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.
```bash
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. After that receipt exists**, the access-engine owner adds an exact record for this memo id, approval id, and binding digest, then the memo is loaded into the live review store. An empty approval id must not be written into policy. Those steps are not done by this preparation.
**4. Answer in the browser.** Sign in at https://decisions.coulomb.social/ with fresh MFA. Open `emergent-profile-adoption-0-2-6`, read the packet, acknowledge the required highlight, and accept, return, or decline. One memo, one answer.
A yes accepts this digest as orientation. 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

View file

@ -0,0 +1,28 @@
{
"kind": "informed-decision-approval-create-intents",
"sitting_id": "infd-sitting-2026-10-04-emergent-profile",
"status": "not-posted",
"posted": false,
"requester_client": "informed-decision-sitting-requester",
"human_control": true,
"pdp_path": false,
"required_count": 1,
"note": "Intents only. Digests are computed by approval-engine at create; do not invent them here. This file does not submit the memo or resolve hub decision d20a9750-2b29-534e-8227-fb866581a6ca.",
"intents": [
{
"memo_id": "emergent-profile-adoption-0-2-6",
"create_client": "informed-decision-sitting-requester",
"binding": {
"action": "accept",
"actor": "informed-decision",
"principal": "emergent-security",
"purpose": "Accept only the non-normative knowledge profile boundary",
"target": {
"id": "emergent-security:knowledge:0.2.6:8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02",
"type": "knowledge-profile",
"system": "emergent-security"
}
}
}
]
}

View file

@ -0,0 +1,53 @@
{
"id": "emergent-profile-adoption-0-2-6",
"version": 1,
"question": "Accept Emergent Security knowledge 0.2.6 as a non-normative NetKingdom agent orientation profile?",
"requested_act": "approve",
"binding_level": "organizational",
"brief": "Accept only the orientation boundary of this exact release; operational authority and remaining review gates stay with their owners.",
"binding": {
"principal": {
"id": "pending-human-session",
"kind": "person",
"display_name": "Pending authenticated reviewer",
"role": "reviewer",
"identifiers": []
},
"target": {
"id": "emergent-security:knowledge:0.2.6:8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02",
"kind": "knowledge-profile",
"label": "Non-normative security orientation",
"environment": "rehearsal",
"requires_new_bind": true
},
"justification": null,
"terms": null
},
"step_kind": "approve",
"packet": [
{
"item_id": "emergent-profile-packet",
"label": "Profile boundary and limitations",
"hash": "sha256:df4a9e0670901aa230d9f33fc9bd2fd1b1f967ef7e2613f840a257cb6b0a1197"
}
],
"highlights": [
{
"id": "orientation-only",
"item_id": "emergent-profile-packet",
"locator": {
"kind": "work_record",
"workplan": "EMERGENT-WP-0002",
"task": "EMERGENT-WP-0002-T02"
},
"note": "Acceptance is not runtime permission or completion of independent review, provider continuity or fleet rollout.",
"required_ack": true,
"severity": "critical"
}
],
"locale": "en",
"ui_release": "informed-decision@0.2.0",
"approval_id": null,
"approval_binding_digest": null,
"sealed": false
}

View file

@ -0,0 +1,49 @@
# Knowledge profile adoption request
Adopt Emergent Security knowledge 0.2.6, release digest 8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02, as a
non-normative orientation profile for coding agents in NetKingdom.
The profile points to existing owners, withholds stale guidance, and separates
human decisions, runtime approvals, PDP decisions, credentials and procedure
records. This asks only to accept that orientation boundary. It does not amend
owner contracts or authorize operational effects, autonomous execution, root,
credential changes or fleet rollout.
Alternatives: return for wording/source corrections; decline this profile;
accept this exact orientation boundary with the documented evidence limits.
Changing the reviewed package requires a new review, not reuse of this answer.
Evidence: knowledge/sources.yaml; docs/decision-runbook-integration.md;
docs/operational-contracts.md; docs/adoption-review.md; docs/evidence/.
Earlier provider reports and owner reviews retain their original release pins.
Whitehat's offline review accepted remediation of the two loaded-package library
findings on the 0.2.3 digest, with disclosed shared-session limits. That
acceptance does not extend to this seal. Continuity and harness proof remain open.
A fresh 0.2.4 Codex, Claude, and Grok session each answered all 28 scenarios.
Implementing review found no unsafe authority recommendation. Recipient
qualifications remain, and that review is not independent ratification.
Those 0.2.4 answers, resume reloads, and four Claude pilots stay pinned to
that digest. They are not evidence for this seal. 0.2.5 reviews Informed
Decision at b4f63732. That revision records local intake delivery,
fresh-login/p01 acceptance, and a dev forwarder that preserves governed
booleans. No listener, submitter grant, custody, or live route is claimed.
A creating approval without a retained receipt is not retried.
0.2.6 names the session owner as the recipient of a provider switch or
compaction reload. glas-harness owns that session boundary. A live
zone-endpoint question goes to zone-engine. The first two-case rerun on this
seal has Codex, Claude, and Grok name zone-engine for that endpoint question
and glas-harness for the reload. They do not use the fixture role label
session-owner. A later two-case rerun, after the probe prompt named the token
session-owner, has all three record that route and keep glas-harness in
sources. Some source lists also name other card or envelope owners. Neither of
those reruns is a full 28-case probe. A later full 28-case probe on this
same seal has each provider preserve the authority boundary. zones is
zone-engine and model-switch is session-owner. Seventeen route tokens match
the fixture in each session, and recipient qualifications remain. Codex has
no exact server model. That probe is not compaction proof, not independent
Whitehat acceptance, and not acceptance of RISK-F-0015. 0.2.4 route results
do not certify this wording.
The draft is unsubmitted. The proposed memo class and review group must be
confirmed by the owner; a synthetic test grant proves format only. INFD-WP-0005
intake rollout remains unfinished. This draft resolves no Statehub decision.

View file

@ -0,0 +1,19 @@
{
"kind": "informed-decision-sitting",
"id": "infd-sitting-2026-10-04-emergent-profile",
"review_group": "net-kingdom-admins",
"principal": "uid=platform-root,ou=people,dc=netkingdom,dc=local",
"status": "prepared",
"hub_decision": "d20a9750-2b29-534e-8227-fb866581a6ca",
"resolves_hub_decision": "never",
"batches": [
"infd-batch-2026-10-04-emergent-profile"
],
"memo_count": 1,
"memo_ids": [
"emergent-profile-adoption-0-2-6"
],
"bind_path": "founder creates the approval in an attended terminal, then exact-record admission, store load, and the founder's own answer",
"note": "Unsigned preparation of the 0.2.6 profile packet. No approval was created, no memo was loaded, and no human answer is recorded.",
"packet_hash": "sha256:df4a9e0670901aa230d9f33fc9bd2fd1b1f967ef7e2613f840a257cb6b0a1197"
}