coulomb/kings-guard
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kings-guard/README.md
tegwick 3d6025ae51 Assent to Staff placement; release control-plane vocabulary (KG-IN-0001) 
Answers gate-house intake KG-IN-0001 / GH-DEC-2026-001 against the
NetKingdom Security Layer Model v0.1.

Assent to all three points, recorded as KG-DEC-2026-001:
- kings-guard declares layer Staff in INTENT.md;
- "control plane" released to the Engine layer across INTENT, SCOPE,
  README, AGENTS and the adjacent-system boundary;
- the posture asymmetry adopted as a repo invariant — already satisfied,
  every EffectorRequest carries an explicit authority_boundary.

Boundary corrections: key-cape and OpenBao are Tooling, so their evidence
is routed through user-engine/access-engine and secrets-engine rather
than read directly.

Finding on the invited challenge to §5: do not weaken the binding rule,
but §4 catalogs kings-guard as owning containment while no engine exposes
a containment surface — the charter is currently undischargeable. Two
rulings requested of gate-house. Three engine gaps declared in INTENT.md.

Residual handed off as KG-IN-0002 (vocabulary sweep of the architecture
spec).

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
2026-08-28 21:47:05 +02:00

1.6 KiB
Raw Blame History

kings-guard

Adaptive security contracts and posture-evaluation scaffold for NetKingdom's immune-architecture work.

Layer: Staff (NetKingdom Security Layer Model v0.1). kings-guard publishes posture and requests bounded response through engine APIs; it never touches Tooling directly and never renders an authorization decision.

Current slice

This repository now contains four aligned pieces:

  • INTENT.md / SCOPE.md for the repo's stable boundary
  • specs/NetKingdomImmuneArchitecture.md for the reference architecture
  • specs/ImmuneContracts.md for the first canonical contract layer
  • src/kings_guard/ plus tests/ for a minimal posture loop scaffold

The current implementation is intentionally narrow. It does not enforce anything. It provides:

  • typed contracts for security genome, phenotype, observation, posture, signal, effector request, and immune memory entry;
  • a minimal posture evaluator that turns a normalized observation into a posture assessment and bounded response hints;
  • a fixture-driven pilot based on qonto-assistant, chosen because it already exposes a security genome record, an audit stream, and a fast local loop.

Repo layout

  • specs/NetKingdomImmuneArchitecture.md
  • specs/ImmuneContracts.md
  • docs/AdjacentSystemBoundary.md
  • docs/pilots/QontoAssistantPosturePilot.md
  • src/kings_guard/
  • tests/
  • workplans/

Dev commands

# preferred, if make + pip are available
make install-dev
make test
make lint
make run-demo

# direct shell fallback used in minimal environments
python3 -m pytest -q
PYTHONPATH=src python3 -m kings_guard.main --pilot qonto-assistant