net-kingdom/canon/standards
tegwick 27a31f3f8f Security Layer Model v0.2 — accepted
All three repositories whose boundaries moved assented, each with a decision
record (flex-auth FLEX-DEC-2026-001, kings-guard KG-DEC-2026-001, ops-warden
ADR-0010), and each returned a finding. v0.2 carries the results and is
accepted; v0.1 is marked superseded and retained because the twelve estate
INTENT review notes cite it.

- §5 restructured into three sanctioned shapes: read-only diagnostics, conduit
  (ops-warden's question, ruled), and declared engine gap (ops-warden's
  amendment, accepted). v0.1 offered only the first, which is narrower than the
  estate as it stands — a rule with no lane for a real sanctioned case gets
  satisfied by relabelling rather than by closing the gap.
- §6.2 added: doctrine must reach the decision as an input claim or a versioned
  policy rule. This is §6.1 applied to gate-house on the same terms it applies
  to engines, drawn back by flex-auth.
- §9 added: the catalog may not assign a capability the rules forbid
  discharging. Containment marked pending an engine surface; degraded-mode
  fallback ruled into access-engine rather than Staff.
- §11: conformance now has three states, distinguishing a tracked gap from an
  undeclared violation.
- §12 made normative, stating that an unsatisfiability finding is a success of
  the conformance loop.
- §13 added: open gaps register, including the unowned approval storage and
  lifecycle capability — recorded, deliberately not assigned.

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
2026-08-28 22:00:31 +02:00
..
credential-management_v0.2.md Add OpenBao runtime secret authority; complete NK-WP-0006/0007/0008 2026-05-20 22:51:20 +02:00
iam-profile_v0.2.md Separate IAM Profile ids and mark v0.2 superseded 2026-08-19 01:09:18 +02:00
iam-profile_v0.3.md docs(canon): reconcile workload and tenant grouping semantics 2026-08-22 14:53:31 +02:00
playbook-capability-contract_v0.1.md feat(orchestration): compose security scenarios 2026-08-23 12:40:52 +02:00
posture-feedback_v0.1.md feat(posture): add deterministic feedback proposals 2026-08-23 13:16:34 +02:00
security-layer-model_v0.1.md Security Layer Model v0.2 — accepted 2026-08-28 22:00:31 +02:00
security-layer-model_v0.2.md Security Layer Model v0.2 — accepted 2026-08-28 22:00:31 +02:00
security-scenario-composition_v0.1.md feat(orchestration): compose security scenarios 2026-08-23 12:40:52 +02:00
security-zones_v0.1.md docs(canon): record security zone adoption 2026-08-22 15:43:52 +02:00
tenancy-posture_v0.1.md feat(posture): add deterministic feedback proposals 2026-08-23 13:16:34 +02:00
tenant-engine-boundary-contract_v0.1.md docs(canon): reconcile workload and tenant grouping semantics 2026-08-22 14:53:31 +02:00
user-engine-boundary-contract_v0.1.md docs: persist user-engine vs net-kingdom integration assessment (new doc + cross-references in SCOPE, boundary contract, guidance, responsibility map, 0018/0019 workplans). Also updated user-engine integration doc to reference it. 2026-06-03 10:33:31 +02:00