Record exact layer review and migrate checker to accepted v0.8

Assistant: codex
Assistant-Model: gpt-6.1-sol
Assistant-Session: 01a126e1-76f8-7643-8cf3-e93336539ade

docs/conformance/2026-10-11-layer-v08-migration.md

@@ -0,0 +1,31 @@
+---
+type: conformance-record
+derived: true
+derived_from: net-kingdom/canon/standards/security-layer-model_v0.8.md
+derived_source_sha256: "3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b"
+updated: "2026-10-11"
+---
+
+# kings-guard accepted v0.8 checker migration
+
+This owner applies GH-WP-0004-T11's post-flip migration to the confirmed
+accepted NetKingdom v0.8 cut, immutable accepted-1 artifact SHA256
+3d8298560069ef471fba28d2b1245fb2309328f231dad1a667cdf0ce5a5a7c8b.
+The checker names that artifact and its local scope in every run. INTENT
+frontmatter remains authoritative and the sidecar remains derived; a
+contradiction is a finding, never hidden by choosing one form. No declaration
+acquires a standard version.
+
+The pin detector follows OpsWarden's A12 r3 reference semantics: standard and
+companion identity values (including nested lists), version-bearing paths and
+standard/companion version keys are pins; unrelated intent/schema/spec versions
+and bare prose provenance are not. Existing local Tooling/contact and capability
+detectors remain in place. Historical version strings in negative fixtures are
+retained. This source migration grants no native capability or runtime authority.
+
+Validation includes the existing local declaration/contact suite and the same
+12-case pin/provenance corpus across all four assigned owners, with exact
+accepted-artifact and scope assertions. The local test counts and staged source
+digests are retained in the coordinating Custodian evidence receipt. Standalone
+checker runs continue to inspect only this repository; no estate-wide compliance
+claim or novel declaration is produced.

docs/reviews/2026-10-10-a11-r2-a12-r3.md

@@ -0,0 +1,75 @@
+# Kings Guard technical owner review — A11 r2 and A12 r3
+
+```yaml
+reviewer: kings-guard-owner (agent kings-guard, codex)
+decision: approved
+reviewed_at: "2026-10-10"
+work_item: KG-WP-ADHOC-2026-10-10-T01
+amendments:
+  - A11 r2
+  - A12 r3
+source_repo: gate-house
+source_revision: 4bd50bfcac850f34e5563ade61fc92103b062f4d
+source_path: docs/amendments/v0.8-section-11-declaration-amendments.md
+source_sha256: 9b454b83c9aeed08ba13dba4d812f5ae6b4293ced9e43088d64cc3cc00b1459d
+section_sha256:
+  A11 r2: 5eac52f955d1dacd1930ff290e4b4d782db9580a431ba350ba278eeb14ab1745
+  A12 r3: 955292aa69f607e7053182fbfee2eb7f29696d38d659251ccccb0de45d77a8e8
+comment: >-
+  INTENT.md's Staff declaration, Responsibility Boundary and Declared engine
+  gaps require one authoritative repository declaration, an agreeing derived
+  sidecar and explicit blocked-clean engine gaps. A11 r2 explicitly permits
+  Kings Guard's single-repository scope and reports outside-catalog runs as
+  voluntary. A12 r3 separates a validity pin from provenance, resolving the
+  precise KG-DEC-2026-005 finding under independent GH-DEC-2026-021 section 1.
+  Approved owner technical review of the exact source revision and section
+  digests above, under KG-WP-ADHOC-2026-10-10-T01; no founder approval or v0.8
+  publication acceptance is recorded here.
+```
+
+The dedicated Kings Guard worker independently read this repository's
+`AGENTS.md` and `INTENT.md`, the exact amendment source and its prior
+`KG-DEC-2026-005` finding. The fleet accepted
+`the-custodian/canon/standards/delegated-owner-review_v0.1.md` permits this
+INTENT-grounded owner review and keeps founder approval as a separate act.
+No human-only reservation for this technical amendment review was found.
+
+A11 r2 preserves Kings Guard's own Staff declaration in `INTENT.md` as the
+source of authority, requires its `layer.yaml` derived form to agree, and
+reports disagreement as a finding. Its new single-repository sentence
+expressly permits this repository's existing checker scope and requires the
+catalog membership statement already printed by that checker. This resolves
+our A11 wording finding in `KG-DEC-2026-005` without changing the Staff boundary.
+
+A12 r3 adopts the distinction requested in `KG-DEC-2026-005`: a version pin
+identifies a standard/companion version to use; a historical citation records
+where a rule came from. Kings Guard benefits from the exemption for three
+sidecar provenance values, so the independent ruling matters.
+`GH-DEC-2026-021` section 1 (resolved by Bernd Worsch; State Hub decision
+`f2e34b44-060c-4367-84bf-0d6d29bc4025`) supplies that ruling. The exact r3 text
+resolves our finding; there is no remaining changes-requested condition for
+these two amendments. Prior r2 dispositions remain immutable history.
+
+Kings Guard continues to judge and propose posture through Engine surfaces.
+This review changes no direct Tooling contact, credential, containment
+actuation, authorization decision/cache, evidence-source classification or
+runtime authority. It covers A11 r2 and A12 r3 alone; it provides no assent to
+other new clause revisions or any unreturned section 9.5 review.
+
+Verification in the Kings Guard checkout on 2026-10-10:
+
+- Exact whole amendment file and both complete section hashes match the
+  retained review unit; Gate House HEAD equals the source revision above.
+- `PYTHONDONTWRITEBYTECODE=1 .venv/bin/python scripts/check_layer_conformance.py`
+  passed, naming accepted v0.7 and Kings Guard's single-repository section 4
+  scope. Declaration forms agree; no direct Tooling client or standing
+  credential was found by this checker.
+- `PYTHONDONTWRITEBYTECODE=1 .venv/bin/python -m pytest tests/test_layer_conformance.py -q -p no:cacheprovider --basetemp=/tmp/security-kings-owner-layer-tests`
+  passed: 25 tests in 1.04 seconds.
+
+The unchanged checker still prints its historical "A12 r2 reach unruled"
+notice for three citations; that wording predates the independent r3 ruling
+and is not a current unresolved finding. This technical review leaves the
+checker and `VALIDATED_AGAINST` at v0.7. Actual v0.8 acceptance/publication and
+post-flip detector convergence are tracked separately by
+`GH-WP-0004-T10`/`GH-WP-0004-T11`.