tegwick
a852d3f1ff
Implements SECRETS-WP-0002 end to end as a uv-managed Python package: - catalog: non-secret lane registry + strict validator (build/test/prod) - stage roles + OpenBao ACL policies; guards refuse wildcards, sys/, identity/, admin names, and cross-stage paths before any backend call - plan/apply: dry-run-first, idempotent policy + approle apply, decision-gated - decisions: State Hub lookup with local-fixture fallback; non-secret evidence to JSONL + hub progress, scrubbed of any value - provision/verify: mode-0600 file import + generated test values; positive/ negative checks that never print the value - exec delivery: `exec --catalog ... -- npm publish` injects the token via a temp .npmrc for the child only, cleaned up on exit/failure/interrupt - ops-warden routing contract + hardening backlog docs - 34 tests incl. live OpenBao integration; scripts/demo-e2e.sh runs the full chain against a throwaway bao dev server Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
47 lines
1.9 KiB
Markdown
47 lines
1.9 KiB
Markdown
# SCOPE
|
|
|
|
> Lightweight boundary for agents and contributors.
|
|
|
|
## One-liner
|
|
|
|
secrets-engine is the workflow and automation interface for approved secret
|
|
custody, delivery, and lifecycle work across build, test, and production, with
|
|
OpenBao as the initial enforcement backend.
|
|
|
|
## Core Idea
|
|
|
|
OpenBao is the vault. secrets-engine is the day-to-day interaction layer that
|
|
connects cataloged secret lanes, approval decisions, stage-specific OpenBao
|
|
roles, safe delivery modes, and non-secret evidence.
|
|
|
|
## In Scope
|
|
|
|
- Non-secret catalog of secret lanes, grants, consumers, stages, and delivery
|
|
modes.
|
|
- Decision-aware planning and apply flows for OpenBao policies, auth roles, and
|
|
metadata.
|
|
- Build, test, and production privilege separation.
|
|
- Safe provisioning, verification, rotation, revocation, and deactivation
|
|
workflows.
|
|
- Exec-time delivery to operators, agents, CI jobs, workloads, and ops-bridge
|
|
tasks without printing raw values.
|
|
- ops-warden routing contract for non-SSH credentials.
|
|
- State Hub non-secret evidence and progress integration.
|
|
- Canonicalization of terms with info-tech-canon.
|
|
|
|
## Out of Scope
|
|
|
|
- Replacing OpenBao as custody, policy, lease, or audit backend.
|
|
- Replacing flex-auth authorization decisions.
|
|
- Replacing user-engine/key-cape identity and claim lifecycle.
|
|
- Issuing SSH certificates, which remains ops-warden responsibility.
|
|
- Owning tunnels or remote transport, which remains ops-bridge responsibility.
|
|
- Storing raw secret values in this repo, State Hub, chat, prompts, or logs.
|
|
- Broad platform-root or platform-admin automation as a steady-state model.
|
|
|
|
## Current State
|
|
|
|
The repo is in bootstrap. Seed intent, PRD, boundary documentation, and an MVP
|
|
workplan are present. The first worker should complete State Hub bootstrap,
|
|
validate the generated repo identity files, then begin the whynot-design npm
|
|
publish token pilot through the `SECRETS-WP-0002` workplan.
|