emergent-security/docs/decisions/profile-adoption-intake.draft.json

{
  "kind": "informed-decision.memo-intake",
  "version": 1,
  "idempotency_key": "emergent-profile-8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02",
  "memo_class": "knowledge-profile",
  "review_group": "net-kingdom-admins",
  "drafted_by": "codex@emergent-security (asserted)",
  "serves": {
    "hub_decision_id": "d20a9750-2b29-534e-8227-fb866581a6ca",
    "resolves": "never"
  },
  "approval_intent": {
    "action": "accept",
    "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"
    }
  },
  "memo": {
    "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
  },
  "packet": [
    {
      "item_id": "emergent-profile-packet",
      "media_type": "text/markdown",
      "content": "# Knowledge profile adoption request\n\nAdopt Emergent Security knowledge 0.2.6, release digest 8d1d6a9d4d07fec7b619618de7dfe2be2254c1790f85f4198c7fe19db9751c02, as a\nnon-normative orientation profile for coding agents in NetKingdom.\n\nThe profile points to existing owners, withholds stale guidance, and separates\nhuman decisions, runtime approvals, PDP decisions, credentials and procedure\nrecords. This asks only to accept that orientation boundary. It does not amend\nowner contracts or authorize operational effects, autonomous execution, root,\ncredential changes or fleet rollout.\n\nAlternatives: return for wording/source corrections; decline this profile;\naccept this exact orientation boundary with the documented evidence limits.\nChanging the reviewed package requires a new review, not reuse of this answer.\n\nEvidence: knowledge/sources.yaml; docs/decision-runbook-integration.md;\ndocs/operational-contracts.md; docs/adoption-review.md; docs/evidence/.\nEarlier provider reports and owner reviews retain their original release pins.\nWhitehat's offline review accepted remediation of the two loaded-package library\nfindings on the 0.2.3 digest, with disclosed shared-session limits. That\nacceptance does not extend to this seal. Continuity and harness proof remain open.\nA fresh 0.2.4 Codex, Claude, and Grok session each answered all 28 scenarios.\nImplementing review found no unsafe authority recommendation. Recipient\nqualifications remain, and that review is not independent ratification.\nThose 0.2.4 answers, resume reloads, and four Claude pilots stay pinned to\nthat digest. They are not evidence for this seal. 0.2.5 reviews Informed\nDecision at b4f63732. That revision records local intake delivery,\nfresh-login/p01 acceptance, and a dev forwarder that preserves governed\nbooleans. No listener, submitter grant, custody, or live route is claimed.\nA creating approval without a retained receipt is not retried.\n0.2.6 names the session owner as the recipient of a provider switch or\ncompaction reload. glas-harness owns that session boundary. A live\nzone-endpoint question goes to zone-engine. The first two-case rerun on this\nseal has Codex, Claude, and Grok name zone-engine for that endpoint question\nand glas-harness for the reload. They do not use the fixture role label\nsession-owner. A later two-case rerun, after the probe prompt named the token\nsession-owner, has all three record that route and keep glas-harness in\nsources. Some source lists also name other card or envelope owners. Neither of\nthose reruns is a full 28-case probe. A later full 28-case probe on this\nsame seal has each provider preserve the authority boundary. zones is\nzone-engine and model-switch is session-owner. Seventeen route tokens match\nthe fixture in each session, and recipient qualifications remain. Codex has\nno exact server model. That probe is not compaction proof, not independent\nWhitehat acceptance, and not acceptance of RISK-F-0015. 0.2.4 route results\ndo not certify this wording.\n\nThe draft is unsubmitted. The proposed memo class and review group must be\nconfirmed by the owner; a synthetic test grant proves format only. INFD-WP-0005\nintake rollout remains unfinished. This draft resolves no Statehub decision.\n"
    }
  ]
}