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 3457ecfb52 build: adopt staged indexes and retain validated dependency lock
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a15374-f59f-7a31-86d2-d23b5d2ed181
2026-10-19 13:15:43 +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 MASON-WP-0015-T02/T03: construct grant installed and probed; Scaleway placeholders created 2026-10-18 12:04:12 +02:00
intakes Record the State Hub id for MASON-IN-0006. 2026-10-18 12:57:08 +02:00
manifests Record CCR-2026-0044 and the founder group step. 2026-10-14 18:44:56 +02:00
plans MASON-WP-0014: reference hub decision e633607e for the approval 2026-10-18 12:57:56 +02:00
policies MASON-WP-0015-T02/T03: construct grant installed and probed; Scaleway placeholders created 2026-10-18 12:04:12 +02:00
registry Record bernd.worsch-3 and the group-ensure route. 2026-10-14 19:05:33 +02:00
scripts MASON-WP-0015-T02/T03: construct grant installed and probed; Scaleway placeholders created 2026-10-18 12:04:12 +02:00
src/ops_mason MASON-WP-0015-T04: structure-only AppRole build, post-build policy check 2026-10-18 12:52:57 +02:00
tests MASON-WP-0015-T04: structure-only AppRole build, post-build policy check 2026-10-18 12:52:57 +02:00
workplans MASON-WP-0015-T06: agent kubeconfig is cluster-admin (MASON-IN-0006) 2026-10-18 12:56:03 +02:00
.custodian-brief.md Record the State Hub id for MASON-IN-0006. 2026-10-18 12:57:08 +02:00
.generated-work-records.json build: adopt staged indexes and retain validated dependency lock 2026-10-19 13:15:43 +02:00
.generated-work-records.mk build: adopt staged indexes and retain validated dependency lock 2026-10-19 13:15:43 +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 MASON-IN-0005: restore ops-mason as the OpenBao builder (ops-mason-construct) 2026-10-18 11:48:27 +02:00
INTENT.md MASON-WP-0015-T06: agent kubeconfig is cluster-admin (MASON-IN-0006) 2026-10-18 12:56:03 +02:00
LICENSE Adopt Target Revenue Source License V1C1 (org-wide preliminary rollout) 2026-07-30 00:42:40 +02:00
Makefile build: adopt staged indexes and retain validated dependency lock 2026-10-19 13:15:43 +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 build: adopt staged indexes and retain validated dependency lock 2026-10-19 13:15:43 +02:00
uv.lock build: adopt staged indexes and retain validated dependency lock 2026-10-19 13:15:43 +02:00
WORK-RECORDS.md Record the State Hub id for MASON-IN-0006. 2026-10-18 12:57:08 +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.