docs: review exact-release profile admission route

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a10238-7ecc-78e2-903d-075f50e913cc

docs/evidence/2026-10-03-emergent-profile-admission-review.md

@@ -0,0 +1,84 @@
+# EMERGENT-WP-0002: exact-release admission and human review route
+
+Scoped review by delegated Codex repository worker, 2026-10-03. Owner source:
+informed-decision b4be6ec7073bfe09fc0e0d639caffb91511725a4. This reviews
+admission requirements, not human acceptance, deployment or memo submission.
+
+Proposed packet: knowledge 0.2.2, package digest
+`19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c`,
+unsigned draft in emergent-security/docs/decisions/profile-adoption-intake.draft.json.
+One question, class `knowledge-profile`, group `net-kingdom-admins`; principal
+`pending-human-session`, asserted drafted_by, no pinned approval, serves hub
+decision `d20a9750-2b29-534e-8227-fb866581a6ca` with `resolves: never`.
+Any reseal requires revalidated packet hashes, target/idempotency digest and
+renewed exact-release review. Historical 0.2.1 reviews are not this acceptance.
+
+## Admission disposition
+
+Not admitted. The class/group are proposals, not a deployed grant. The local
+intake validator exists (INFD-WP-0005 T02), but the separate authenticated
+`POST /v1/memos` listener is still T04 todo. Neither
+`deploy/intake-submitters.json` nor `deploy/review-groups.json` exists.
+No live endpoint or identity was probed. With this actual 0.2.2 draft,
+`validate_submission(..., submitter_id="state-hub", grant=None)` refuses
+`submitter_unknown at $`. A synthetic SubmitterGrant is validation evidence
+only and cannot establish real admission.
+
+`net-kingdom-admins` appears in the existing Access Engine sitting policy, but
+that does not admit this memo or `knowledge-profile`. Access Engine's explicit
+record branch requires the exact memo id/version, approval id and approval
+binding digest. Do not reuse another sitting's entry or invent a receipt.
+
+## Current attended route and exact remaining steps
+
+The working precedent is
+`docs/batches/2026-10-03-provisioning-window/OPERATOR.md` A1–A6. Its commands,
+sitting ids and approvals belong to another question and cannot be reused
+verbatim for this adoption. No generic live intake command is presently ready.
+
+1. Owner prepares one dedicated adoption sitting from the reviewed unsigned
+   draft, with exact release/digest, packet, required highlights and current
+   principal/group requirements. Validate offline and preserve the draft.
+2. The founder uses the owner's attended requester-login lane in their own
+   terminal to create the approval through approval-engine. Preserve returned
+   approval id and engine-computed digest in a sanitized receipt. Do not ask an
+   agent to read a credential or act as the human approver.
+3. Access Engine owner prepares the exact-record policy admission for this
+   memo, preserving existing records. Founder gives the specific go for the
+   production pin/review-service admission changes; owners execute their
+   existing build/deploy routes and verify positive and negative admission.
+   No deployment is authorized by this review.
+4. The owner attaches the approval pin and exact KeyCape recipient principal
+   to the dedicated bound copy, then loads it into the live review store by
+   the existing operator tools. The unsigned draft remains evidence of drafting.
+5. The founder signs into the known decision overview with fresh MFA, opens
+   this exact memo, reads the packet and acknowledges required highlights,
+   then answers individually. Only that authenticated human disposition binds.
+   Preserve presentation/view_hash and approval evidence independently.
+6. Reconcile the adoption decision separately: this draft says `resolves: never`.
+   An accepted profile boundary still does not close provider continuity,
+   independent assurance, runtime authority or fleet distribution requirements.
+
+The preferred future route is INFD-WP-0005, which removes per-memo human posing
+steps after its implementation/rollout gates pass. Admit a verified workload
+submitter (first planned: State Hub), class and review group by reviewed owner
+configuration; resolve the named KeyCape recipient; use a projected token with
+audience informed-decision-intake, not an asserted body identity or human token.
+T05 requester custody, T06 Access Engine attribute admission, T07 evidence /
+notification, T08 State Hub forwarding and T10 founder-approved rollout remain
+their existing tasks. This review implements no self-admission or provisioning.
+
+## Doctrine and unresolved conditions
+
+Gate House reply `4a290496-5aa7-4488-a01d-f8fde925a54b` confirms no doctrine
+requires a human act at pose time; its GH-DEC-2026-023 draft is proposed and
+the founder rules it. Conditions include live approval read and exact pin
+comparison independent of the PDP allow; view_hash excluded from PDP context;
+human_control true; authentication-derived principal; revocable submitter
+admission; independent review of submitter/class changes; asserted drafting
+origin when State Hub forwards. Preserve declared attribution and PEP-carried
+fact gaps. This receipt does not turn that doctrine reply into a grant.
+
+No API memo submission, approval creation, credential access, provisioning,
+human answer, live deployment or hub-decision resolution occurred. Work remains
+on INFD-WP-0005 and the existing EMERGENT-WP-0002 adoption gate.

workplans/INFD-WP-0005-frictionless-decision-intake.md

@@ -181,3 +181,14 @@ Roll out, pose one real memo end to end with no human step before the answer,
 record positive and negative evidence, then retire
 `create_sitting_approvals.*`, `attach_compact_bindings.py` and
 `load_sitting_memos.py` to fallback status.
+
+
+## Emergent profile admission review — 2026-10-03
+
+`docs/evidence/2026-10-03-emergent-profile-admission-review.md` records the
+0.2.2 exact-release draft's knowledge-profile / net-kingdom-admins admission
+requirements and current attended A1–A6 route. No deployed intake submitter or
+class grant was found; the real draft refuses submitter_unknown without a grant.
+The alternative authenticated intake remains T04–T10. Gate House's T09 reply
+4a290496 is described with its proposed-record conditions, without changing
+authority or task states. No submission, provisioning or human answer occurred.