The agent responsible to create, change, maintain and tear down access routes with new credentials, tokens, policies, etc inside net-kingdom. Ops-mason is responsible to build the security infrastructure as required and defined by architecture documents as a base for ops-warden..
Find a file
tegwick 20b92e2d46 MASON-WP-0010-T03: source review complete; attended owner checklist
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 903097@bnt-lap001
Assistant-Session: aa320c8f-c3fa-46e7-8541-0b58e1e45d23
2026-10-17 04:31:10 +02:00
builds Prepare seven-repository reuse-surface reader construction revision 2 2026-10-15 01:39:47 +02:00
bundles Enforce readiness tiers and reconcile blocked workplans 2026-09-28 11:40:57 +02:00
docs fix(cases): expose explicit versioned type roots in Mason CLI 2026-10-16 07:51:41 +02:00
intakes MASON-IN-0003: ask fluid-telegram for the adapter deployment identity 2026-10-09 10:45:03 +02:00
manifests Record CCR-2026-0044 and the founder group step. 2026-10-14 18:44:56 +02:00
plans Prepare seven-repository reuse-surface reader construction revision 2 2026-10-15 01:39:47 +02:00
policies WP-0009-T05 invariant (ii) verified; survey policy covers keycape-services roles; Forgejo plan re-rendered 2026-10-10 14:13:02 +02:00
registry Record bernd.worsch-3 and the group-ensure route. 2026-10-14 19:05:33 +02:00
scripts MASON-WP-0012: named-role login without session reuse, diagnosis receipt, capabilities-self proof (NK-WP-0051-T06) 2026-10-14 23:48:11 +02:00
src/ops_mason fix(cases): expose explicit versioned type roots in Mason CLI 2026-10-16 07:51:41 +02:00
tests fix(cases): expose explicit versioned type roots in Mason CLI 2026-10-16 07:51:41 +02:00
workplans MASON-WP-0010-T03: source review complete; attended owner checklist 2026-10-17 04:31:10 +02:00
.custodian-brief.md MASON-WP-0010-T03: source review complete; attended owner checklist 2026-10-17 04:31:10 +02:00
.gitignore intake: hand off legacy MASON identifier scheme 2026-08-22 11:33:34 +02:00
.repo-classification.yaml chore(registrar): bind MASON-IN-0001 residual 2026-08-22 11:34:25 +02:00
AGENTS.md Require the SEC-DSM decision procedure on new credentials. 2026-10-11 23:41:31 +02:00
INTENT.md Replace ops-mason-build with read-only ops-mason-survey grant (MASON-IN-0004) 2026-10-07 10:44:24 +02:00
LICENSE Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-30 00:42:40 +02:00
pyproject.toml build: add guarded Kubernetes plane executor 2026-08-22 11:23:38 +02:00
README.md build: add guarded Kubernetes plane executor 2026-08-22 11:23:38 +02:00
SCOPE.md Bind OpenBao builds to approved inputs and secure credential delivery 2026-09-28 11:55:39 +02:00
WORK-RECORDS.md Record MASON-WP-0011 in the State Hub index. 2026-10-14 18:21:50 +02:00

ops-mason

The builder of NetKingdom security infrastructure — creates, changes, maintains, and tears down access routes, credentials, tokens, and policies so that ops-warden always has something real to route to.

The four-phase process

  1. Construction plan — given an access demand, draft what needs building, respecting/extending/compacting existing structure first.
  2. Review and optimize — self-review the plan against what already exists, for consistency and ease of use.
  3. Executive summary — the one mandatory human decision gate: render who gets what access, for how long, and what it costs to reverse.
  4. Build — once approved, execute the plan.

See INTENT.md for the full responsibility boundary against ops-warden, OpenBao, flex-auth, and key-cape.

Guarded Kubernetes planes

Small Kubernetes security foundations can use the fail-closed ops-mason plane workflow. It pins source manifests and object identities, validates cluster context/RBAC/dependencies/drift, requires an approved construction plan plus exact digest for apply, and produces metadata-only evidence and a non-executing rollback plan.

See docs/kubernetes-plane.md.