tegwick
06d0a1e690
The blocker asked whether `secrets-engine exec --catalog` generalizes over arbitrary OpenBao lanes. Asked 2026-08-11, chased 08-15, never answered. Rather than chase a third time, read their code. It generalizes by construction: catalog.py takes mount and path as plain fields, `kv` is a general kind, and six delivery modes are supported. What exists is two catalog entries -- warden-sign and whynot-design-npm-publish -- which are exactly the two lanes this register already marks native. So the blocker was misframed for ten days. Not "can the engine do this" but "who authors the entries and who operates them", which is smaller and had never been put to them. Register now says that, and ops-warden has offered to author all seven entries against their schema for them to accept or reject. Applying the rule this repo already had and missed twice this week: re-read a blocker before trusting it. A blocker is a claim about the world at a date. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| capabilities | ||
| flex-auth | ||
| indexes | ||
| policy | ||
| routing | ||
| README.md | ||
Capability Registry
Markdown-first capability index for federation and reuse planning.
Authoring
- Copy a capability entry template (see reuse-surface
templates/capability-entry.template.md). - Add the row to
indexes/capabilities.yaml. - Run
reuse-surface validatefrom a checkout with the CLI installed. - Merge to
mainand verify publish withreuse-surface establish --publish-check.
Federation contract: reuse-surface docs/RegistryFederation.md.