diff --git a/docs/conformance/2026-10-03-emergent-knowledge-021-review.md b/docs/conformance/2026-10-03-emergent-knowledge-021-review.md
new file mode 100644
index 0000000..7a199cd
--- /dev/null
+++ b/docs/conformance/2026-10-03-emergent-knowledge-021-review.md
@@ -0,0 +1,82 @@
+# Gate House doctrine review — Emergent knowledge 0.2.1
+
+Disposition: no blocking doctrine conflict found in the non-normative estate
+profile. Generic Emergent v0.8 remains an offline reference, not adopted estate
+doctrine. Human adoption and publication dispositions remain open.
+
+## Reviewed artifact and limits
+
+Knowledge 0.2.1; digest `d8ef41bacd2c6551ae3b87628004a5df6943928be1c93eb01e09efc6ad782767`; emergent-security commit `f9cba6fb35425f74e34401b1baf09f6057ace493`.
+
+Reviewed by the Codex repository worker, 2026-10-03, under the user's
+EMERGENT-WP-0002 owner-review delegation. This is an owner-scoped documentary
+review by an agent, not human assent, adoption, independent whitehat evidence,
+or a runtime grant. The existing adoption decision
+`d20a9750-2b29-534e-8227-fb866581a6ca` remains open.
+
+Read the artifact's adoption-review, closure-attempt, integration-profile decision,
+operational contracts, integration map, source matrix, all 14 cards, unsigned
+exact-release adoption draft, knowledge-maintenance, and T02/T08/T09. Retrieval
+with `--repositories /home/worsch` reported 0.2.1 and the digest above; all 24
+owners were `verified-files`, `live_state_verified: false`. File verification
+is distinct from live readiness. No inventoried source content was changed.
+
+The unsigned memo asks only whether this exact non-normative orientation
+boundary is accepted. Its `knowledge-profile` class and `net-kingdom-admins`
+group are proposals requiring informed-decision's real submission/admission
+route. A synthetic validation grant proves format only. Do not sign, seal,
+bind, answer, or infer approval from this review or silence.
+
+## Owner sources and findings
+
+Reviewed gate-house@6f80ba860453416f44b83ff2709ee21b6e89e456: INTENT, SCOPE,
+authority-context.v1, ADR-001/002, GH-DEC-2026-001/-004/-005/-010/-016/-017/-018/-019,
+GH-WP-0004 and the v0.8 assent-round disposition. Read the current draft
+GH-DEC-2026-023 as a draft, not a governing accepted ruling.
+
+| Conflict | Doctrine disposition |
+| --- | --- |
+| G9 historical Gate-House broker | Superseded by GH-DEC-2026-001 and current INTENT. Gate House establishes doctrine and teaching; secrets-engine owns credential lifecycle, OpenBao custody, ops-warden routing/SSH. The compatibility card resolves this correctly without rewriting the historical reference. |
+| Reference evaluator / sole PDP | Offline AUTONOMOUS is not an access-engine allow. authority-context.v1 defines what must be expressible, while access-engine resolves facts and decides. No compiler or second decision surface is accepted. |
+| Containment and posture | Proposal-only Kings Guard matches the current profile; adaptive posture cannot manufacture authority. Effects need an implemented and authorized owner route. |
+| HOT/build assumptions | Task delegation, structure-only approved plan exceptions, human-reserved decisions, production founder go and harness stops govern. Generic HOT defaults cannot override them. No close-down relaxation was introduced by this documentary review. |
+| Context and evidence | Principal, actor and runtime identity remain distinct. Approval fact, PDP envelope, presentation hash, custody and emission guarantees remain distinct. Missing-event routing to the source owner agrees with GH-DEC-2026-018. |
+| Publication versions | Emergent reference v0.8 and NetKingdom security-layer-model v0.8 are different artifacts. NetKingdom v0.7 remains accepted while v0.8 is proposed under GH-DEC-2026-019/GH-WP-0004; adopting the orientation cannot flip that standard. |
+
+## Teaching feedback and next gate
+
+The actual NetKingdom 0.2.0 pilot correctly distinguishes doctrine, sole PDP,
+credential lifecycle and custody, and refuses reference AUTONOMOUS as a grant.
+It is one read-only Claude scenario, evaluated by the implementing Codex session;
+it does not certify 0.2.1, all providers, continuity or operational effects.
+Gate House teaching should use that distinction plus missing-event/source-owner,
+withdrawn-procedure refresh and model-switch/task-owner scenarios. Preserve full
+Claude 0.2.1 27/28 and its targeted pass separately; do not average them into a
+stable full-corpus pass. Grok current-release and independent review remain open.
+
+Proposed division: Gate House maintains doctrine learning objectives, scenario
+expectations and curriculum links; Emergent Security maintains the executable
+knowledge bundle and source inventory; NetKingdom publishes the estate profile
+pointer. SecurityCanon maintains the meaning of imported authority terms.
+Neither Gate House nor NetKingdom copies the 14-card bundle as a second mutable
+source. Distribution and harness readiness remain Custodian/Glas owner work.
+
+Approval-ready question for the existing decision: accept only this exact
+orientation boundary, return it for corrections, or decline? Publication and
+curriculum ownership should be explicitly recorded alongside the human answer;
+fleet rollout remains gated by EMERGENT-WP-0002-T07/T08/T09.
+
+Review work record: GH-WP-ADHOC-2026-10-03-T02. The review is complete; the
+existing EMERGENT decision/tasks retain adoption and rollout, rather than
+duplicating their pending task lists here.
+
+## Subsequent corrected-release condition
+
+The coordinating worker reports a planned 0.2.2 remediation for post-load card
+tamper/lifecycle invalidation and serving the bytes that were verified. This
+review retains its original 0.2.1 version/digest and does not certify the fix.
+Before adopting a replacement, record its exact digest/commit, check the changed
+content/source and unsigned memo freshness, repeat affected retrieval/scenario
+checks, and obtain independent whitehat close-out. Unchanged vocabulary/doctrine
+findings may be carried forward explicitly; changed content requires review.
+The proposed publication filename must follow the release actually accepted.
diff --git a/workplans/ADHOC-2026-10-03.md b/workplans/ADHOC-2026-10-03.md
index 625f4f6..40991a2 100644
--- a/workplans/ADHOC-2026-10-03.md
+++ b/workplans/ADHOC-2026-10-03.md
@@ -39,3 +39,18 @@ Pending, not opened: if a named consumer later depends on the sample API,
 re-declaring railiance-clock as an Engine in the PIP role needs a §4 catalog row.
 That requires a gate-house decision record and a normal workplan, opened at that
 time and not before.
+
+## Review Emergent Security 0.2.1 doctrine boundary
+
+```task
+id: GH-WP-ADHOC-2026-10-03-T02
+status: done
+priority: medium
+```
+
+Completed the authorized repository-scoped documentary review under
+EMERGENT-WP-0002. Evidence: docs/conformance/2026-10-03-emergent-knowledge-021-review.md.
+No blocking doctrine conflict in the non-normative estate profile. No human
+assent, operational adoption, canon acceptance flip or runtime effect asserted.
+The existing open decision d20a9750-2b29-534e-8227-fb866581a6ca and
+EMERGENT-WP-0002-T02/T08/T09 retain the approval/publication/pilot gates.