tegwick
cbf6828061
flex-auth enforced its ops-warden pin (FLEX-WP-0016 T03) and the gate verified clean against it: readiness exits 0, decision:f3f7c88f9585582a, anonymous /v1/check now 401. Everything needed to set policy.enabled: true was in place. It stays false, by decision. policy.enabled is a single repo-wide boolean, and with fail_closed: true it makes flex-auth a hard dependency of every warden sign — including the certs the ops-bridge tunnels depend on, one of which carries the policy call itself. Uniform enforcement across an estate being actively rebuilt hardens the access needed to perform the rebuild. The repo already refuses one-dimensional posture: WP-0015 shipped environment and maturity axes, WP-0029 added organization_posture. A global flag ignores all three. ADR-0006 records that enforcement belongs to a zone, and binds future work — a zone-blind enforcement flag is out of order, not merely unwise. WARDEN-WP-0032 drafts the zone model, leading with the ownership question: whether this is ops-warden's to own or NetKingdom canon to consume (ADR-0005). WP-0031 is finished with T05 cancelled and resuming as WP-0032-T05. Also replaces the hand-run kubectl port-forward with a managed ops-bridge tunnel, flex-auth-ops-warden-railiance01 (-L 19090:10.43.1.165:8080). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2.6 KiB
Architecture
Our rules are ADRs — docs/adr/
The decisions that govern this repo live in docs/adr/ as addressable records,
not in wiki prose. Read docs/adr/README.md first; it explains the one
distinction that matters here.
| ADR | Rule |
|---|---|
ADR-0001 |
The routing catalog is a pointer layer, never a second copy of an owner's procedure |
ADR-0002 |
ops-warden is a transparent conduit, never a secret broker |
ADR-0003 |
Cover gaps, but never silently own them |
ADR-0004 |
High-risk lanes refuse raw value streaming to agent sessions |
ADR-0005 |
Implement one lane narrowly, route everything else |
ADR-0006 |
Enforcement is zone-scoped, never a global flag |
Owned versus inherited — check owner: before changing anything
Every ADR carries owner: in its frontmatter, and it decides what you are allowed
to do with the rule:
owner: ops-warden— ours. We are bound by it and we may change it. Changing one means writing a superseding ADR, not editing the decision in place.- any other owner — inherited. We follow it; we do not own it. Dispute it through that owner's process; never amend it here.
Everything in docs/adr/ today is owner: ops-warden. Rules we merely follow —
NetKingdom canon, the IAM profile, the credential-management standard — are cited,
never copied in. Copying them would recreate the second-source-of-truth failure
ADR-0001 exists to prevent.
Naming collision, worth knowing. ADR-001 (three digits) in
workplan-convention.md and session-protocol.md is the-custodian's ADR
establishing the workplan convention across the whole estate. It is inherited and
not ours to change. Our records are four-digit — ADR-0001 … ADR-0005 — and live
in this repo. When writing, say "the-custodian's ADR-001" if that is what you mean.
Precedence
If a wiki page, playbook, or .claude/rules/ file disagrees with an ADR, the ADR
is right and the other file is a defect — fix it rather than working around it.
The rule files are agent-facing operational instructions derived from these
decisions; they should cite an ADR rather than restate its reasoning.
Publication
These ADRs are publishable through policy-nexus at policy.coulomb.social, which
requires title, status and owner, renders owner in the page header and in the
index, and records source repo, path and revision digest in its manifest. Ownership
survives the repo boundary. policy-nexus publishes and never writes back: the file
here is the source of truth.
Quick Reference
~/state-hub/mcp_server/TOOLS.md — MCP tool reference