Open security core for dev sec ops on kubernetes
Find a file
tegwick b5cb1520d8
Some checks are pending
CI Smoke / host-smoke (push) Waiting to run
CI Smoke / container-smoke (push) Waiting to run
Complete attended reset-role observation with verified receipt
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a18e2d-f513-7742-b8e7-12af0b744ff3
2026-10-31 14:00:35 +01:00
.claude docs: workplan-first agent guidance prose (CUST-WP-0055 T04 batch 2) 2026-07-08 16:41:16 +02:00
.forgejo/workflows NK-WP-0056-T09: prepare synthetic journey identity for founder run 2026-10-31 12:42:36 +01:00
.githooks feat(creds): implement NK-WP-0004 Credential Management Foundation 2026-03-20 23:39:35 +00:00
.repo-manager Security Layer Model v0.5 — four reviews, nine changes 2026-08-29 02:54:25 +02:00
canon NK-WP-0056-T01 done: Bounded Execution Admission v0.1 (proposed) 2026-10-31 13:55:18 +01:00
capabilities/playbooks NK-WP-0048-T09: keycape-client entry point and declaration 2026-10-08 23:03:00 +02:00
docs Complete attended reset-role observation with verified receipt 2026-10-31 14:00:35 +01:00
examples NK-WP-0056-T01 done: Bounded Execution Admission v0.1 (proposed) 2026-10-31 13:55:18 +01:00
generated/coordination-frame Adopt shared hourly coordination frame and prepare guarded runtime patches 2026-10-15 20:45:06 +02:00
history NK-WP-0054: record the founder's state-hub attribution decisions 2026-10-25 00:08:31 +02:00
identity-provisioner identity-provisioner: platform group boundary test without pytest 2026-10-29 22:48:54 +01:00
intakes build: adopt staged records and retain pending owner handoff evidence 2026-10-19 13:32:59 +02:00
keys feat(creds): implement NK-WP-0004 Credential Management Foundation 2026-03-20 23:39:35 +00:00
local-identity Report bootstrap audit failures and track cadence adoption work 2026-10-03 22:42:57 +02:00
projects/nk-rehearsal Add nk-rehearsal project for the NK-WP-0044-T05 pack rehearsal 2026-10-02 22:31:20 +02:00
registry docs(recovery): accept retained token material and audit continuity 2026-10-16 21:14:23 +02:00
runbooks Follow the access-engine CLI rename: ./cmd/flex-auth -> ./cmd/access-engine 2026-10-10 15:28:05 +02:00
security-case-type-revisions NK-WP-0048-T34: integrate the corrected F3 owner configuration inverse text into 1.3 2026-10-23 07:08:41 +02:00
security-case-types NK-WP-0048: run keycape check-config before any registry patch 2026-10-10 15:28:05 +02:00
security-cases NK-WP-0056-T09: SecurityCase nk-synthetic-journey accepted by the founder 2026-10-31 12:51:09 +01:00
sso-mfa Prepare attended read-only classification for accepted reset subject 2026-10-31 13:54:51 +01:00
tests Prepare attended read-only classification for accepted reset subject 2026-10-31 13:54:51 +01:00
tools NK-WP-0056-T01 done: Bounded Execution Admission v0.1 (proposed) 2026-10-31 13:55:18 +01:00
wiki Add CLAUDE.md, wiki protoplans, and NK-WP-0001 workplan 2026-02-28 17:21:51 +01:00
workplans Complete attended reset-role observation with verified receipt 2026-10-31 14:00:35 +01:00
.generated-work-records.json build: adopt staged records and retain pending owner handoff evidence 2026-10-19 13:32:59 +02:00
.generated-work-records.mk build: derive coordination receiver from staged owner sources 2026-10-19 13:44:36 +02:00
.gitignore build: keep generated orientation brief local and untracked 2026-10-19 13:50:40 +02:00
.repo-classification.yaml Human-review .repo-classification.yaml (CUST-WP-0050 follow-up) 2026-06-22 17:56:17 +02:00
.sops.yaml fix(security): constrain SOPS writes and custody argument handoff 2026-10-13 21:03:24 +02:00
AGENTS.md NK-WP-0054: security review; standard draft-3 as a SecurityCanon profile; agent security quickstart 2026-10-24 23:12:37 +02:00
CLAUDE.md NK-WP-0054: security review; standard draft-3 as a SecurityCanon profile; agent security quickstart 2026-10-24 23:12:37 +02:00
CONFIG.md Adopt shared hourly coordination frame and prepare guarded runtime patches 2026-10-15 20:45:06 +02:00
DECISIONS.md Decision for KeyCape Implementation Language Go 2026-03-26 09:21:17 +01:00
INTENT.md Declare net-kingdom's own layer and record positions on the v0.8 hold and §11 amendments. 2026-09-21 12:36:10 +02:00
LICENSE Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-29 23:43:45 +02:00
Makefile NK-WP-0056-T01 done: Bounded Execution Admission v0.1 (proposed) 2026-10-31 13:55:18 +01:00
README.md Accept security layer v0.8 from confirmed native review 2026-10-11 01:53:56 +02:00
SCOPE.md build: keep generated orientation brief local and untracked 2026-10-19 13:50:40 +02:00
SECURITY-COMPANION.md Accept security layer v0.8 from confirmed native review 2026-10-11 01:53:56 +02:00
WORK-RECORDS.md Complete attended reset-role observation with verified receipt 2026-10-31 14:00:35 +01:00

NetKingdom

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
  • Security scenario composition — deterministic, plan-only capability and trust composition
  • 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.