LANE-KIND accepts an attended step on a login lane, or on an attended-change lane whose session_lane resolves to an active, reviewed login lane. keycape-attended-case-change -> session_lane key-cape-oidc-login (OW-1.3-C1). consumer-owner-deployment and apps-consumer-handover -> pending-owner-confirmation: no catalog login lane authenticates a railiance-apps operator session. apps-consumer-handover risk: high (KERNEL-2, change effect). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Assistant: claude-code Assistant-Model: opus Assistant-Process: 903097@bnt-lap001 Assistant-Session: aa320c8f-c3fa-46e7-8541-0b58e1e45d23 |
||
|---|---|---|
| .. | ||
| 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.