Proposed by ops-mason (MASON-WP-0001-T05), built and approved 2026-07-27 (Bernd Worsch). New pointer-only entry mirroring agent-harness-binky-mail-approle's shape: AppRole login, no operator present, scoped to exactly one KV path (reins/rein-openweights/openrouter, new reins/ KV v2 mount -- no existing mount fit without widening scope beyond what was approved). status: draft until the founder completes paste-once-provision and glas-harness/GLAS-WP-0002-T02's live verification succeeds. Co-Authored-By: Claude Sonnet 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.