tegwick
97c7eea1da
The standard is accepted at v0.7 with a working companion. v0.7 wrote the §3.4 agent-principal rules that v0.6 announced and never wrote — our finding — and credits kings-guard for it. Our other two findings landed too: the actuation row is no longer attributed to us, and §17 records kings-guard as drafter of the emission-cadence declaration. INTENT.md now carries the declaration in frontmatter (layer: Staff, conformance_state: blocked-clean) as the companion asks, plus prose in our own voice. Adopted: the four agent-principal rules; the evidence doctrine and our obligations under it; containment reframed as proposal throughout. Direction of Evolution stage 3 rewritten — it described integrating with effectors to actuate, which §9.2 forbids — and stage 5 now carries the constraint that federated memory may not become a state plane. SCOPE.md gains evidence classification, the cadence draft, and stream-completeness judgment as in-scope; actuation, standing credentials, and becoming a state plane as explicitly out. history/2026-08-29-layer-model-v0.7-scope-intent-review.md assesses the adapted documents against the implementation. The finding: the documents are now correct and the code has not caught up. Nine gaps, G1-G8 carried by KG-WP-0003, G9 remaining as KG-IN-0002. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UEtvmYUBP2fDtirJGWn5MW Assistant: claude-code Assistant-Model: opus Assistant-Process: 4014379@bnt-lap001 Assistant-Session: 4af9e20f-1768-4afc-951b-b507784e382b
116 lines
4.8 KiB
YAML
116 lines
4.8 KiB
YAML
# kings-guard — NetKingdom security layer declaration
|
|
#
|
|
# Framework: net-kingdom/canon/standards/security-layer-model_v0.7.md
|
|
# Assent: decisions/decisions.md KG-DEC-2026-001 (kings-guard's own voice, §11)
|
|
# Validate: python3 scripts/check_layer_conformance.py
|
|
#
|
|
# §11 (v0.6) requires a machine-readable declaration: prose cannot distinguish a
|
|
# declaration from a transcribed review. Form adapted from ops-warden's
|
|
# reference implementation, offered under §11.
|
|
#
|
|
# kings-guard's position is unusual and this file is shaped to state it exactly:
|
|
# there are NO Tooling contacts. Not a narrow one, not a read-only one. The
|
|
# capabilities that would need them sit at zero instead. Under §11 that is
|
|
# BLOCKED-CLEAN, which MUST NOT rank below conforming.
|
|
|
|
schema_version: "0.1"
|
|
framework: netkingdom-security-layer-model
|
|
standard_version: "0.7"
|
|
repository: kings-guard
|
|
layer: staff
|
|
declared_by: decisions/decisions.md#KG-DEC-2026-001
|
|
declared_at: "2026-08-29"
|
|
|
|
# §4 catalog entry, transcribed so drift between the catalog and this file is
|
|
# visible. The standard is authoritative for the row; this records what we
|
|
# understand ourselves to have been assigned.
|
|
# §3.4 — the four rules binding the agent principal. kings-guard offered to
|
|
# assent to these sight-unseen before they were written into v0.7.
|
|
agent_principal_rules:
|
|
no_standing_credential: true
|
|
tool_use_shapes: ["5.2-conduit", "engine-api"]
|
|
memory_is_not_a_state_plane: true
|
|
reconstructable_as_caller: true
|
|
|
|
catalog_entry:
|
|
owns:
|
|
- adaptive defence and judgment
|
|
- observation of Staff-reachable sources
|
|
pending:
|
|
- identity observation
|
|
- secret observation
|
|
proposes_but_does_not_own:
|
|
# §9.2 — actuation is an Engine concept held at zero. kings-guard proposes
|
|
# containment and never performs it. This is not our gap to close.
|
|
- containment
|
|
|
|
# §5 / §11: every direct contact with a Tooling-layer system (a §4 Tooling row),
|
|
# one entry each. Empty is a claim, and scripts/check_layer_conformance.py is
|
|
# what makes it checkable rather than asserted.
|
|
tooling_contacts: []
|
|
|
|
# §11 requires non-Tooling clients to be recorded "so the check is total".
|
|
non_tooling_clients:
|
|
- id: state-hub-work-records
|
|
target: state-hub
|
|
layer: not-catalogued
|
|
operation: "HTTP to the Custodian State Hub for work records and progress events"
|
|
write: true
|
|
note: >-
|
|
Outside §5 by the v0.5 scope rule: "Tooling-layer system" means a §4
|
|
Tooling row, and state-hub is not one. Recorded, not policed. Carries no
|
|
security authority and no secret payload.
|
|
|
|
# §11 blocked-clean. These are NOT §5.3 declared gaps: there is no contact to
|
|
# declare. Fields follow the §5.3 shape so one register can hold both kinds
|
|
# (§13 now carries the state column that keeps them distinct — raised by
|
|
# kings-guard against v0.4).
|
|
unowned_capabilities:
|
|
|
|
- id: authentication-assurance-evidence
|
|
state: unowned-capability
|
|
capability: >-
|
|
Token assurance, attestation outcomes and authentication anomalies exposed
|
|
as an engine surface, for identity-drift posture.
|
|
intended_owner: "identity layer + audit-core"
|
|
owner_status: "access-engine declined (v0.6 §13); reproposed, not assented"
|
|
blocked_on: >-
|
|
No engine exposes authentication evidence. key-cape is Tooling, so §5
|
|
forbids the direct route, and the capability stays at zero rather than
|
|
being taken locally.
|
|
review: "2026-11-28"
|
|
consequence: "identity-drift posture lane stays fixture-driven"
|
|
|
|
- id: secret-use-evidence
|
|
state: unowned-capability
|
|
capability: >-
|
|
Lease, revocation, mount and rotation metadata exposed as an engine
|
|
surface, for secret-abuse posture.
|
|
intended_owner: secrets-engine
|
|
owner_status: proposed
|
|
blocked_on: >-
|
|
No engine exposes secret-use evidence. OpenBao is Tooling; same reasoning
|
|
as above.
|
|
review: "2026-11-28"
|
|
consequence: "secret-abuse posture lane stays fixture-driven"
|
|
|
|
- id: actuation-surface
|
|
state: unowned-capability
|
|
capability: >-
|
|
Reduce authority, require step-up, isolate a workload — as a deterministic
|
|
engine API carrying a decision record.
|
|
intended_owner: "access-engine + runtime PEPs"
|
|
owner_status: "proposed; access-engine has not reviewed (FLEX-DEC-2026-002)"
|
|
blocked_on: >-
|
|
Ruled in v0.6 §9.2 to be an Engine concept, unowned and held at zero.
|
|
kings-guard proposes containment and does not own it, so this row is
|
|
recorded here as a dependency, not as a kings-guard gap to close.
|
|
review: "2026-11-28"
|
|
consequence: "no containment is possible anywhere in the estate"
|
|
|
|
# §5.1 read-only diagnostic observation of Tooling: none declared, none taken.
|
|
# §5.2 conduit: none. kings-guard runs no tool under a caller's identity.
|
|
declared_shapes:
|
|
"5.1": []
|
|
"5.2": []
|
|
"5.3": []
|