railiance-platform's go-ahead (message 20973a9c) after key-cape confirmed the secret format and the T05 probe passed. Promotion checklist: owner confirmed, playbook, owner-native exec, probe evidence, rotation and delegation present; routing test added. The live oidc-browser-relying-party type is now plannable. CredentialRouting lists the lane and adds fluid-telegram-operator to drafts. WP-0044-T03 now waits only on the Forgejo case materializing (MASON-WP-0010-T03). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 427672@bnt-lap001 Assistant-Session: a0a2367e-4697-440c-a4e5-9713c009f6d8 |
||
|---|---|---|
| .. | ||
| capabilities | ||
| flex-auth | ||
| generated | ||
| 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.