ops-warden/registry
tegwick 207d29e8d1 feat(case): attended-change lane kind with session_lane; grade apps-consumer-handover high
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
2026-10-17 12:13:49 +02:00
..
capabilities docs(reuse): establish reviewed NetKingdom security capabilities 2026-10-14 06:41:08 +02:00
flex-auth WARDEN-WP-0040-T02: compile activity-core's backup-daily declaration 2026-10-09 00:13:47 +02:00
generated chore(registry): regenerate high-risk data paths for catalog a14376c 2026-10-17 12:08:52 +02:00
indexes docs(reuse): establish reviewed NetKingdom security capabilities 2026-10-14 06:41:08 +02:00
policy WARDEN-WP-0029: implement plan front door, org posture, desk, freshness 2026-07-18 16:59:37 +02:00
routing feat(case): attended-change lane kind with session_lane; grade apps-consumer-handover high 2026-10-17 12:13:49 +02:00
README.md Add capability registry scaffold (REUSE-WP-0014-T06 B04) 2026-06-16 01:56:08 +02:00

Capability Registry

Markdown-first capability index for federation and reuse planning.

Authoring

  1. Copy a capability entry template (see reuse-surface templates/capability-entry.template.md).
  2. Add the row to indexes/capabilities.yaml.
  3. Run reuse-surface validate from a checkout with the CLI installed.
  4. Merge to main and verify publish with reuse-surface establish --publish-check.

Federation contract: reuse-surface docs/RegistryFederation.md.