statehub register + repo-seed template scaffold (CLAUDE.md, .claude/rules/, registry/). INTENT.md and SCOPE.md rewritten from the generated stub to match net-kingdom's ratified tenant-engine-boundary-contract_v0.1.md (Purpose, Responsibility Boundary, Non-Goals). topic_slug corrected from the auto-assigned custodian default to netkingdom, matching key-cape and user-engine. TEN-WP-0001 (bootstrap) complete: files reviewed/refined, stack decided (Python 3.12 + FastAPI, matching qonto-assistant's convention), first real workplan seeded. TEN-WP-0002 drafted: service skeleton, domain model (tenant/grouping/ capability-role/plan-grant), storage layer, and the three boundary-contract API surfaces (cache-read for key-cape, live-lookup for flex-auth with an explicit fail-closed requirement, write API behind a WriteAuthorizer seam since real flex-auth integration is a declared non-goal for this pass). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
12 lines
474 B
Markdown
12 lines
474 B
Markdown
# 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`.
|