coulomb/ops-warden
4
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions

WARDEN-WP-0029: implement plan front door, org posture, desk, freshness
All checks were successful
CI Smoke / host-smoke (push) Successful in 1s
Details
CI Smoke / container-smoke (push) Successful in 2s
Details

Browse source 
Ship posture-aware access planning: organization_posture=build (axis C),
catalog freshness warnings, warden plan verdicts, localhost founder desk,
and playbook/agent guidance that retire /tmp file-drop patterns.

Compose route catalog + handoff rather than a second routing layer.
This commit is contained in:
tegwick 2026-07-18 16:59:37 +02:00
parent 5c6b71b83b
commit 5149946a4c
18 changed files with 1690 additions and 102 deletions
Download patch file Download diff file Expand all files Collapse all files

17
.claude/rules/credential-routing.md
View file

@ -10,18 +10,26 @@ other credential need belongs to another subsystem. **Do not** message
### Lookup (do this first)
**Always plan before drafting any founder credential step** (WARDEN-WP-0029):
```bash
warden plan "<describe your need>" --json
# verdict: autonomous | founder_required | unroutable
```
```bash
warden route find "<describe your need>" --json
warden route show <catalog-id> --json
```
Requires the `warden` CLI from `~/ops-warden` (`uv tool install .` or `uv run warden`).
If a known lane is missing, reinstall from checkout (stale bundled catalog).
| Agent runtime | How to orient |
| --- | --- |
| **Codex / Grok** (shell, HTTP State Hub) | `warden route` commands above; inbox `to_agent=ops-warden` is for coordination, not secret vending |
| **Claude Code** (MCP when available) | `get_domain_summary("custodian")` for workplans; **still** use `warden route` for credential ownership |
| **llm-connect** (inference service) | Never put secret retrieval in prompts; route custody to OpenBao/operator paths surfaced by `warden route` |
| **Codex / Grok** (shell, HTTP State Hub) | `warden plan` first; inbox `to_agent=ops-warden` is for coordination, not secret vending |
| **Claude Code** (MCP when available) | `get_domain_summary("custodian")` for workplans; **still** use `warden plan` / `warden route` for credential ownership |
| **llm-connect** (inference service) | Never put secret retrieval in prompts; route custody via `warden plan` |
### Quick routing table
@ -36,9 +44,12 @@ Requires the `warden` CLI from `~/ops-warden` (`uv tool install .` or `uv run wa
### Anti-patterns (do not do these)
- Drafting founder steps ("paste PAT to `/tmp`", "click admin UI") without `warden plan`
- `POST /messages/` to `ops-warden` asking for `ISSUE_CORE_API_KEY`, `OPENROUTER_API_KEY`, etc.
- Inventing `warden secret`, `warden login`, `warden bao`, `warden tunnel` — they do not exist
- Pasting secrets into Git, State Hub, workplans, logs, or chat
- Steady-state **file drops** of credentials under `/tmp` (use `warden desk` paste-once
or `warden access --out/--exec/--wrap`)
- **Reading a secret value onto a captured stdout.** `bao kv get <path>` (full table)
or `bao kv get -field=X` piped/redirected/run in an agent session dumps the value
into a logged context — the 2026-07-16 disclosure. To *verify* a lane use