Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 943911@bnt-lap001
Assistant-Session: fc322940-1c8e-4bed-ab39-86cec99f23a0
NetKingdom is the canonical security architecture, integration boundary, and
bootstrap/reference implementation for NetKingdom environments. It defines
identity, tenancy, credential, workload-zone, and security-composition
contracts while leaving provider and Railiance execution in their owning
repositories.
The dynamic, self-optimizing security platform is the long-term direction in
INTENT.md, not a claim about current delivery.
Orientation
SCOPE.md — what this repo owns, current state, and when it is relevant
SECURITY-COMPANION.md — start here. The working
form of the security layer model: what to declare, what binds you, what you may
never claim about evidence, and the two things the estate cannot do yet
Security layer model — the
statute the companion serves (accepted 2026-08-29): how the security estate is
layered (Taxonomy / Tooling / Engines / Staff) and what each layer may own
Posture feedback — deterministic,
proposal-only posture and evidence remediation findings
Emission cadence security profile
— NetKingdom obligations over the InfoTechCanon declaration contract;
proposed pending owner-instance migration
Security Infrastructure Documents
secrets-engine security infrastructure boundary
defines how secrets-engine participates in the NetKingdom security
infrastructure and how it interacts with OpenBao, flex-auth, user-engine,
ops-warden, ops-bridge, info-tech-canon, State Hub, and agents.
tegwick
e536ce8133