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
repo-manager 77a2eadd28 repo.work.create_intake MASON-IN-0002
correlation_id: 8a9408fd-c863-4b65-ad0a-d514f7d10c13
reason: Request own-voice layer declaration under §11
source: repo-manager

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 2564823@bnt-lap001
Assistant-Session: 2a7ed827-4928-4b9f-8613-9135c9cadfe9
2026-08-28 23:03:29 +02:00
bundles build: add guarded Kubernetes plane executor 2026-08-22 11:23:38 +02:00
docs build: provision and verify Whitehat foundational plane 2026-08-22 11:26:49 +02:00
intakes repo.work.create_intake MASON-IN-0002 2026-08-28 23:03:29 +02:00
manifests/whitehat-plane build: add guarded Kubernetes plane executor 2026-08-22 11:23:38 +02:00
plans feat(mason): deliver and verify the forge read credential 2026-08-27 23:46:42 +02:00
policies feat(mason): describe stored credentials, and stop the grant rewriting itself 2026-08-28 11:43:08 +02:00
scripts feat(mason): describe stored credentials, and stop the grant rewriting itself 2026-08-28 11:43:08 +02:00
src/ops_mason build: provision and verify Whitehat foundational plane 2026-08-22 11:26:49 +02:00
tests build: provision and verify Whitehat foundational plane 2026-08-22 11:26:49 +02:00
workplans chore(registrar): assign State Hub identifiers 2026-08-28 11:52:56 +02:00
.custodian-brief.md chore(consistency): sync task status from DB [auto] 2026-08-27 22:49:39 +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 feat(mason): scoped, named OpenBao sessions instead of borrowing yours 2026-08-28 11:04:26 +02:00
INTENT.md Point layering note at the published standard 2026-08-28 21:21:08 +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 Tighten the ops-warden boundary after reviewing its actual repo 2026-07-27 00:44:37 +02:00
WORK-RECORDS.md chore(work-records): regenerate 2026-08-28 11:52:37 +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.