coulomb/gate-house
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Record the founder's Kubernetes change gate and ops-mason's §6.4 exception (GH-DEC-2026-022, GH-IN-0004).

Browse source 
No engine owns ops-mason's Kubernetes contact: the gate on ADMINISTER @
realm:kubernetes is quality, tiered by ADR-0006 readiness_state. Founder plan
approval is recorded as an accepted exception against §6.4 obligation 1 and
the §13.1 row, not a change to §6.4. No canon edited, no amendment drafted.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Assistant: claude-code
Assistant-Model: opus
Assistant-Process: 63291@bnt-lap001
Assistant-Session: 8bd77868-ca68-4f49-bb1e-d539ecc0d703
This commit is contained in:
tegwick 2026-09-21 14:35:48 +02:00
parent 8f035ee8be
commit 398b91ce38
2 changed files with 226 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

35
intakes/intakes.md
View file

@ -214,3 +214,38 @@ updated: '2026-09-21T00:00:00.000000Z'
outcome: ruled
state_hub_intake_id: "01a0c155-b5a3-7de4-b19f-12b1bc658729"
```
## GH-IN-0004 — Which engine, if any, should own ops-mason's contact with the Kubernetes API
```yaml
id: GH-IN-0004
kind: intake
title: Which engine, if any, should own ops-mason's contact with the Kubernetes API
status: closed
origin: cross-repo
origin_ref: ops-mason INTENT.md frontmatter, tooling_contacts kubernetes-plane-apply
(ops-mason@0ff263a)
priority: medium
owner: gate-house
requested_by: ops-mason
lane: red
description: 'ops-mason declares its kubectl apply contact (src/ops_mason/kubernetes_plane.py)
as a section 5.3 engine gap with intended_owner null. Its blocked_on says Kubernetes
is not catalogued in section 4, that ops-mason reads the cluster as Tooling by character
(section 3.2), and that the question was raised with gate-house as a catalog question.
Gate House had not recorded it until now. The earlier founder decision accepting
plan approval as the phase-4 gate (the-custodian docs/ops-mason-plan-approval-gate-decision.md)
left it open explicitly.
Closed by the founder''s decision of 2026-09-21, the-custodian docs/kubernetes-change-gate-decision.md
(the-custodian@e3d0d13), recorded here as GH-DEC-2026-022. No engine owns the contact.
The gate on ADMINISTER @ realm:kubernetes is a quality gate, not an authorization
decision, tiered by railiance-master ADR-0006 readiness_state. The section 5.3 gap
stays declared with intended_owner null by decision. A section 4 catalog row for the
Kubernetes API is noted in GH-DEC-2026-022 as a candidate for the cut after v0.8,
not drafted.'
created: '2026-09-21T12:30:00.000000Z'
updated: '2026-09-21T12:30:00.000000Z'
outcome: ruled
```