Add WP-0030 delegation register; refresh INTENT and SCOPE
Founder directive: ops-warden works with, never replaces or duplicates, secrets-engine / tenant-engine / user-engine. Covering an unfilled gap is acceptable only as a tracked interim with a named intended owner. - INTENT §9 "Cover gaps, but never silently own them"; success criterion 7; tenant-engine and user-engine added to the literacy table; non-goal on permanently owning another component's lane - WP-0030 (proposed): delegation: metadata, backfill, warden route gaps, promotion gate, publish the register to owner repos - history/2026-08-11-delegation-surface-assessment.md: 2 of 24 lanes carry exec_owner; 11 proxies record no intended owner - SCOPE refreshed to 2026-08-11 (was 6 workplans behind); completeness C5 -> C4 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
95ecfe51e2
commit
9d42dd5abd
6 changed files with 512 additions and 15 deletions
104
SCOPE.md
104
SCOPE.md
|
|
@ -17,7 +17,7 @@ access guidance aligned with NetKingdom canon.
|
|||
|
||||
---
|
||||
|
||||
## Where we are (2026-07-01)
|
||||
## Where we are (2026-08-11)
|
||||
|
||||
ops-warden **issues short-lived SSH certificates and routes every other credential
|
||||
need to the subsystem that owns it.** SSH signing is **production-verified** on
|
||||
|
|
@ -59,12 +59,28 @@ contract smoke (`--sign-smoke`); the playbook leads with the gate and the pilot
|
|||
(`agt-state-hub-bridge`) is handed to ops-bridge. The live tunnel cutover is
|
||||
ops-bridge's to execute.
|
||||
|
||||
**INTENT alignment:** SSH issuance mission met in production. ops-warden workplans
|
||||
through WP-0021 are finished; WP-0022 (audit) and WP-0023 (INTENT–SCOPE closeout)
|
||||
ship in July 2026. Remaining distance is in other repos' lanes: ops-bridge running
|
||||
the cert_command pilot cutover, flex-auth runtime deployment (FLEX-WP-0007, unblocks
|
||||
`policy.enabled: true`), and the owner-driven WP-0015 canon landing — plus ongoing
|
||||
operator hygiene.
|
||||
**Credential hygiene and the policy front door** shipped through July 2026:
|
||||
disclosure hygiene and rotation guidance (WP-0026 — `warden taint`,
|
||||
`warden rotate-guide`, agent read-boundary on high-risk lanes), the tenant secret
|
||||
custody pattern (WP-0028, first lane binky company email IMAP), experiential memory
|
||||
across worker/agent sessions (WP-0024), the Forgejo admin PAT lane (WP-0025), and the
|
||||
posture-aware policy front door (WP-0029 — `warden plan`, `warden desk`, declared
|
||||
`organization_posture: build` as a third axis). WP-0027 (tamper-resistant governance,
|
||||
mass rotation/lockdown) is drafted and sits in `backlog`.
|
||||
|
||||
**Delegation register** is the open question (WP-0030, proposed). ops-warden fronts
|
||||
11 catalog lanes as a caller-identity proxy with no record of which component *should*
|
||||
own that front door. The primitive to delegate exists and is proven
|
||||
(`exec_owner`/`exec_command` — secrets-engine for npm publish, the credential broker
|
||||
for warden-sign) but is used by 2 of 24 lanes. See
|
||||
`history/2026-08-11-delegation-surface-assessment.md`.
|
||||
|
||||
**INTENT alignment:** SSH issuance mission met in production. All ops-warden workplans
|
||||
through WP-0029 are finished except WP-0027 (`backlog`) and WP-0030 (`proposed`).
|
||||
Remaining distance is in other repos' lanes: ops-bridge running the cert_command pilot
|
||||
cutover, flex-auth runtime deployment (FLEX-WP-0007, unblocks `policy.enabled: true`),
|
||||
the owner-driven WP-0015 canon landing, and — newly named — the missing owner front
|
||||
doors that keep ops-warden holding interim lanes (secrets-engine, tenant-engine).
|
||||
|
||||
### Issue vs route
|
||||
|
||||
|
|
@ -84,6 +100,12 @@ ops-warden executes exactly one lane with its own authority and routes/assists t
|
|||
Full role and boundary: `wiki/AccessRouting.md`. The catalog is a **pointer layer** —
|
||||
it never restates an owner's procedure (authored `steps` exist only for the SSH lane).
|
||||
|
||||
**Interim by default.** SSH issuance is the only lane ops-warden owns permanently.
|
||||
Where it proxies or assists, it is covering a need no component fronts yet — a
|
||||
legitimate service, but a *tracked gap*, retired to the owner once their front door
|
||||
exists (INTENT §9). Recording that intent per lane is WP-0030; today only
|
||||
`whynot-design-npm-publish` and `ops-warden-warden-sign-token` carry it.
|
||||
|
||||
Gap analysis: `history/2026-07-01-intent-scope-gap-analysis.md` (current);
|
||||
`history/2026-06-24-intent-scope-gap-analysis.md` (prior);
|
||||
`history/2026-06-18-post-wp0008-intent-scope-reassessment.md` (SSH lane);
|
||||
|
|
@ -101,14 +123,15 @@ Gap analysis: `history/2026-07-01-intent-scope-gap-analysis.md` (current);
|
|||
| NetKingdom evolution reflected in docs | Met |
|
||||
| Non-SSH secrets stay out of ops-warden | Met |
|
||||
| Workload posture / maturity model for secret-flow blockers | Met — two-axis standard + descriptors + conformance checker + dev doubles (WP-0015) |
|
||||
| Every execution position explicitly permanent or interim with a named owner | **Not met** — 2 of 24 lanes carry `exec_owner`; 11 proxy lanes record no intended owner (WP-0030) |
|
||||
|
||||
**Maturity vector:** `D5 / A5 / C5 / R4` (Discovery / Availability / Completeness / Reliability)
|
||||
**Maturity vector:** `D5 / A5 / C4 / R4` (Discovery / Availability / Completeness / Reliability)
|
||||
|
||||
| Dimension | Level | Meaning today |
|
||||
| --- | --- | --- |
|
||||
| D5 | Discovery | Routing wiki + security map + pointer catalog + NK canon cross-links |
|
||||
| A5 | Availability | CLI + `warden route` + `warden access` advisory & proxy front door + `warden policy` + opt-in policy gate + agent `--json` |
|
||||
| C5 | Completeness | All ops-warden lanes shipped — SSH (prod), routing, access assist, posture conformance, cert_command pilot gate, two owner-native exec routes documented (secrets-engine npm, credential broker warden-sign). Open items are external: flex-auth prod flip + ops-bridge live cutover |
|
||||
| C4 | Completeness | All ops-warden lanes shipped — SSH (prod), routing, access assist, posture conformance, cert_command pilot gate, disclosure hygiene, tenant custody, policy front door. **Down from C5:** delegation is unrecorded on 11 of 24 lanes, so ops-warden's interim positions are not distinguishable from designed ones (WP-0030) |
|
||||
| R4 | Reliability | Live OpenBao sign + credential-broker policy-gate smoke evidence on Railiance (2026-07-01) |
|
||||
|
||||
---
|
||||
|
|
@ -165,6 +188,19 @@ for the rest.
|
|||
- **Unified audit trail** (WP-0022): append-only `audit.jsonl`, secret-material guard,
|
||||
instrumentation on sign/access/worker paths, `warden activity` CLI merging legacy
|
||||
logs + optional State Hub notes (`wiki/AuditTrail.md`)
|
||||
- **Experiential memory** (WP-0024, `src/warden/memory.py`) — recorded outcomes feed
|
||||
routing and coordination; no secret values, guardrail allowlist unchanged
|
||||
- **Disclosure hygiene** (WP-0026): `warden taint <catalog-id>` (KV `custom_metadata`,
|
||||
no data read), `warden rotate-guide`, safe fetch transports (`--out` / `--exec` /
|
||||
`--wrap`) with refusal to stream to non-terminal stdout, and the agent read-boundary
|
||||
on `risk: high` lanes (exit 7 when `WARDEN_AGENT_ID` is set)
|
||||
- **Tenant secret custody** (WP-0028): tenant vs `platform/workloads/...` path
|
||||
convention, policy/CCR/catalog ownership, first lane `binky-company-email-imap`
|
||||
- **Policy front door** (WP-0029): `warden plan "<need>" [--json]` returning
|
||||
`autonomous` / `founder_required` (typed act) / `unroutable` (CCR stub);
|
||||
`warden desk` loopback founder surface (approve, OIDC login, paste-once provision
|
||||
straight into OpenBao); `organization_posture: build` as posture axis C; catalog
|
||||
freshness reporting on `warden route list` and in plan JSON
|
||||
|
||||
### Stewardship (documentation and alignment)
|
||||
|
||||
|
|
@ -198,8 +234,25 @@ for the rest.
|
|||
|
||||
| WP | Focus |
|
||||
| --- | --- |
|
||||
| WP-0017 | Access front-door discoverability |
|
||||
| WP-0018 | `whynot-design-npm-publish` — first concrete secret lane (production-exercised) |
|
||||
| WP-0019 | Route provisioned secret-exec lanes to secrets-engine (`exec_owner` pattern) |
|
||||
| WP-0020 | Coordination worker (`warden worker`) |
|
||||
| WP-0021 | Scheduled worker tick (systemd --user timer, kill switch) |
|
||||
| WP-0022 | Unified audit trail + `warden activity` |
|
||||
| WP-0023 | INTENT–SCOPE alignment closeout |
|
||||
| WP-0024 | Experiential memory across worker/agent sessions (`src/warden/memory.py`) |
|
||||
| WP-0025 | Forgejo admin PAT OpenBao lane (CCR-2026-0006) |
|
||||
| WP-0026 | Credential disclosure hygiene — `warden taint`, `warden rotate-guide`, agent read-boundary, safe fetch transports |
|
||||
| WP-0028 | Tenant secret custody pattern — tenant vs platform paths; first lane binky company email IMAP |
|
||||
| WP-0029 | Policy front door — `warden plan`, `warden desk`, `organization_posture: build` third axis |
|
||||
|
||||
### Open ops-warden work
|
||||
|
||||
| WP | Status | Focus |
|
||||
| --- | --- | --- |
|
||||
| WP-0027 | `backlog` | Tamper-resistant credential governance + mass rotation/lockdown (Strand B follow-on to WP-0026) |
|
||||
| WP-0030 | `proposed` | Delegation register — record intended owner + blocker on every interim lane, `warden route gaps`, promotion gate |
|
||||
|
||||
Remaining production distance is also in other repos' lanes (see Known gaps).
|
||||
|
||||
|
|
@ -212,6 +265,8 @@ Remaining production distance is also in other repos' lanes (see Known gaps).
|
|||
| Principals sync warden ↔ railiance-infra | ops-warden + infra | `scripts/check_principals_drift.py` — operator runs periodically |
|
||||
| NK-WP-0009 joint SSH tutorial | net-kingdom | Parallel coordination track |
|
||||
| WP-0015 canon landing (generic `WorkloadMaturityLevel` + M0-M3 requirements) | net-kingdom + info-tech-canon | ops-warden drafted + offered (coordination msgs); owner-driven landing |
|
||||
| Owner front doors for workload secret lanes | secrets-engine | 6 lanes proxied by ops-warden that `secrets-engine exec` could front, as WP-0019 did for npm publish |
|
||||
| Owner front door for tenant secret lanes | tenant-engine | WP-0028 defined the custody pattern; 3 tenant lanes still fronted by ops-warden proxy |
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -231,6 +286,9 @@ Remaining production distance is also in other repos' lanes (see Known gaps).
|
|||
- OpenBao / Vault cluster deployment → `railiance-platform`
|
||||
- Human admin SSH key generation (self-service `ssh-keygen`)
|
||||
- Session recording, SIEM, SSO / Teleport at scale
|
||||
- **Permanently owning another component's lane.** Covering an unfilled gap is in
|
||||
scope and expected; keeping it once secrets-engine / tenant-engine / user-engine
|
||||
can front it — or holding it without recording that it is interim — is not (INTENT §9)
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -284,12 +342,24 @@ Remaining production distance is also in other repos' lanes (see Known gaps).
|
|||
- **Audit + activity:** WP-0022 shipped — `warden activity`, `wiki/AuditTrail.md`
|
||||
- **INTENT closeout:** WP-0023 shipped — INTENT refresh, production flip/cutover
|
||||
checklists, catalog promotion cadence, broker hint on missing `VAULT_TOKEN`
|
||||
- **Active work:** none open in ops-warden after WP-0022/0023; remaining distance is
|
||||
other repos' lanes
|
||||
- **Disclosure hygiene:** WP-0026 shipped — `warden taint`, `warden rotate-guide`,
|
||||
safe fetch transports (`--out`/`--exec`/`--wrap`), agent read-boundary on `risk: high`
|
||||
lanes (`wiki/playbooks/agent-read-boundary.md`)
|
||||
- **Tenant custody:** WP-0028 shipped — tenant vs platform path convention; first lane
|
||||
`binky-company-email-imap`. Front door is still an ops-warden proxy (tenant-engine gap)
|
||||
- **Policy front door:** WP-0029 shipped — `warden plan "<need>"` (autonomous /
|
||||
founder_required / unroutable), `warden desk` founder interaction surface, declared
|
||||
`organization_posture: build` as a third posture axis, catalog freshness reporting
|
||||
- **Delegation:** 24 catalog lanes — 1 executed by ops-warden (SSH), 2 delegated via
|
||||
`exec_owner`, 11 proxied with **no intended owner recorded**, 10 route-only. Addressed
|
||||
by WP-0030 (proposed)
|
||||
- **Active work:** WP-0027 (`backlog`), WP-0030 (`proposed`); remaining production
|
||||
distance is other repos' lanes
|
||||
- **Integration docs:** cert_command migration, token hygiene (broker-first), principals
|
||||
drift (`wiki/playbooks/`)
|
||||
- **Latest assessment:** `history/2026-07-01-intent-scope-gap-analysis.md`
|
||||
- **Latest workplans:** WP-0022 (audit), WP-0023 (INTENT–SCOPE closeout) — shipped July 2026
|
||||
- **Latest assessment:** `history/2026-08-11-delegation-surface-assessment.md`
|
||||
- **Latest workplans:** WP-0029 (policy front door) shipped July 2026; WP-0030
|
||||
(delegation register) proposed 2026-08-11
|
||||
|
||||
---
|
||||
|
||||
|
|
@ -335,7 +405,9 @@ Downstream: `ops-bridge` (primary), kaizen agents, CI automations, human operato
|
|||
| `railiance-platform` | OpenBao deployment and platform secrets |
|
||||
| `flex-auth` | Authorization; policy package shipped (FLEX-WP-0006); runtime deploy FLEX-WP-0007 |
|
||||
| `key-cape` | Identity / IAM Profile lightweight mode |
|
||||
| `secrets-engine` | Owner-native secret-exec front door (`secrets-engine exec/route`); ops-warden routes provisioned secret lanes to it (WP-0019) |
|
||||
| `secrets-engine` | Owner-native secret-exec front door (`secrets-engine exec/route`); ops-warden routes provisioned secret lanes to it (WP-0019) and holds 6 more as interim proxies pending its front doors |
|
||||
| `tenant-engine` | Intended owner of tenant/client secret front doors; ops-warden holds 3 tenant lanes as interim proxies (WP-0028 pattern, WP-0030 register) |
|
||||
| `user-engine` | End-user identity/account lifecycle; no ops-warden lane today — route rather than absorb |
|
||||
| `state-hub` | Workplan registry |
|
||||
|
||||
---
|
||||
|
|
@ -388,7 +460,9 @@ keywords: [access, credential, secret, npm, token, api-key, openbao, key-cape, l
|
|||
| `wiki/AuditTrail.md` | Unified metadata-only audit + `warden activity` |
|
||||
| `wiki/playbooks/catalog-lane-promotion.md` | draft → active catalog promotion checklist |
|
||||
| `wiki/CertCommandInterface.md` | cert_command contract |
|
||||
| `history/2026-07-01-intent-scope-gap-analysis.md` | Current INTENT↔SCOPE gap analysis |
|
||||
| `history/2026-08-11-delegation-surface-assessment.md` | Current assessment — where ops-warden covers gaps and who should own them |
|
||||
| `workplans/WARDEN-WP-0030-delegation-register.md` | Delegation register plan (proposed) |
|
||||
| `history/2026-07-01-intent-scope-gap-analysis.md` | Prior INTENT↔SCOPE gap analysis |
|
||||
| `workplans/WARDEN-WP-0023-intent-scope-alignment-closeout.md` | Alignment closeout plan |
|
||||
| `history/2026-06-24-intent-scope-gap-analysis.md` | Prior gap analysis |
|
||||
| `history/2026-06-27-workload-security-posture-charter.md` | WP-0015 posture/conformance charter |
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue