Security Layer Model v0.3 — assign approvals and maturity

v0.2 recorded the approval object as the one open architectural hole, and
carried a latent instance of its own §9.1 rule: gate-house was catalogued as
owning conformance review with no engine to act through. Two engines were
seeded to close both.

- §9.4: the approval object goes to approval-engine — not Staff (§3.4 forbids
  the runtime state), not access-engine (an evaluator owning what it evaluates
  is self-dealing), not audit-core (append-only is the opposite property).
  access-engine consumes approvals as input claims under §6.2; audit-core takes
  the tamper-evident evidence. Operative state and evidence record are separate
  artifacts with separate owners.
- §9.5: graded progression goes to maturity-engine. gate-house judges and
  proposes; maturity-engine computes and remembers. Carries the guardrail that
  a level may never gate a decision directly — under §6.1 that would be a
  second decision point by the graded back door.
- §4 catalog gained both engines; §13 register updated.

Status proposed: the new engines are seeded by owner direction with no other
side to assent yet, and the approval evidence half needs audit-core's assent.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2564823@bnt-lap001
Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9

canon/standards/security-layer-model_v0.2.md

@@ -3,7 +3,7 @@ id: netkingdom-security-layer-model-v0.2
 type: standard
 title: "NetKingdom Security Layer Model v0.2"
 domain: netkingdom
-status: accepted
+status: superseded
 version: "0.2"
 supersedes: canon/standards/security-layer-model_v0.1.md
 owner: gate-house
@@ -14,6 +14,7 @@ last_reviewed: "2026-08-28"
 review_interval: 3m
 source_revision: "gate-house@4f618b4"
 standard_token: security-layer-model_v0.2
+superseded_by: canon/standards/security-layer-model_v0.3.md
 assented_by:
   - "flex-auth FLEX-DEC-2026-001"
   - "kings-guard KG-DEC-2026-001"
@@ -28,6 +29,11 @@ related:
 
 # NetKingdom Security Layer Model v0.2
 
+> **Superseded 2026-08-28 by [v0.3](security-layer-model_v0.3.md)**, which assigns
+> the approval and maturity concepts §13 recorded as unowned. The assent record in
+> §14 remains the basis on which the model was accepted; v0.3 changes §4, §9, and
+> §13 only.
+
 ## 1. Purpose
 
 This standard states how NetKingdom's IT-security estate is layered, and what