generated from coulomb/repo-seed
tegwick
c366fc4a4e
Some checks failed
ci / validate-registry (push) Has been cancelled
Add Gitea CI workflow for registry validation, reuse-surface overlaps and catalog commands, generated catalog artifacts, and documentation updates closing gap analysis priorities 9-11.
79 lines
2.8 KiB
Markdown
79 lines
2.8 KiB
Markdown
# Capability Catalog
|
|
|
|
**Domain:** helix_forge
|
|
**Updated:** 2026-06-15
|
|
**Entries:** 6
|
|
|
|
Generated by `reuse-surface catalog`. Do not edit manually.
|
|
|
|
## helix_forge
|
|
|
|
### Feature Availability Evaluation
|
|
|
|
- **ID:** `capability.feature-control.evaluate`
|
|
- **Vector:** D5 / A4 / C3 / R3
|
|
- **Owner:** feature-control
|
|
- **Path:** `registry/capabilities/capability.feature-control.evaluate.md`
|
|
- **Summary:** Evaluate whether a feature is active, hidden, disabled, or unavailable for a subject in context.
|
|
|
|
**Known limitations:**
|
|
- bulk rule management is not yet covered
|
|
- agent-specific simulation remains a known gap
|
|
|
|
### Feature Rollout Control
|
|
|
|
- **ID:** `capability.feature-control.rollout`
|
|
- **Vector:** D4 / A2 / C2 / R1
|
|
- **Owner:** feature-control
|
|
- **Path:** `registry/capabilities/capability.feature-control.rollout.md`
|
|
- **Summary:** Gradually expose features to subjects across tenants, domains, groups, or cohorts using rollout rules and staged availability.
|
|
|
|
**Known limitations:**
|
|
- distinguish carefully from capability.feature-control.evaluate
|
|
|
|
### Identity Subject Resolution
|
|
|
|
- **ID:** `capability.identity.subject-resolution`
|
|
- **Vector:** D3 / A0 / C1 / R0
|
|
- **Owner:** identity-canon
|
|
- **Path:** `registry/capabilities/capability.identity.subject-resolution.md`
|
|
- **Summary:** Resolve who or what is acting in a context by mapping principals, accounts, actors, and identifiers to a stable subject model.
|
|
|
|
**Known limitations:**
|
|
- resolver artifacts are not yet available
|
|
|
|
### Identity Vocabulary Canonicalization
|
|
|
|
- **ID:** `capability.identity.vocabulary-canonicalize`
|
|
- **Vector:** D4 / A0 / C2 / R0
|
|
- **Owner:** identity-canon
|
|
- **Path:** `registry/capabilities/capability.identity.vocabulary-canonicalize.md`
|
|
- **Summary:** Define and maintain an implementation-neutral vocabulary for identity-related concepts across overlapping domains.
|
|
|
|
**Known limitations:**
|
|
- source-note backfill is incomplete
|
|
- mappings may remain candidate until evidence review completes
|
|
|
|
### Capability Registration
|
|
|
|
- **ID:** `capability.registry.register`
|
|
- **Vector:** D3 / A3 / C2 / R2
|
|
- **Owner:** reuse-surface
|
|
- **Path:** `registry/capabilities/capability.registry.register.md`
|
|
- **Summary:** Register a new capability so it becomes visible for planning and implementation reuse.
|
|
|
|
**Known limitations:**
|
|
- manual index updates are required after adding an entry
|
|
- duplicate detection is guidance-only in the MVP
|
|
|
|
### Workstream And Task Coordination
|
|
|
|
- **ID:** `capability.statehub.workstream-coordinate`
|
|
- **Vector:** D4 / A4 / C3 / R2
|
|
- **Owner:** state-hub
|
|
- **Path:** `registry/capabilities/capability.statehub.workstream-coordinate.md`
|
|
- **Summary:** Track active workstreams, tasks, progress, and consistency across domain repositories through a local-first coordination service.
|
|
|
|
**Known limitations:**
|
|
- requires running State Hub locally or via tunnel
|