generated from coulomb/repo-seed
Complete REUSE-WP-0004: CI, overlap detection, and catalog generation
Some checks failed
ci / validate-registry (push) Has been cancelled
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.
This commit is contained in:
78
docs/CapabilityCatalog.md
Normal file
78
docs/CapabilityCatalog.md
Normal file
@@ -0,0 +1,78 @@
|
||||
# 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
|
||||
@@ -265,12 +265,18 @@ own evidence (e.g. feature-control at R3).
|
||||
|
||||
### Next recommended work
|
||||
|
||||
| Priority | Gap | Outcome | Status |
|
||||
|---|---|---|---|
|
||||
| 9 | Catalog site | `reuse-surface catalog` → MD + HTML | Closed (WP-0004) |
|
||||
| 10 | Overlap detection | `reuse-surface overlaps` | Closed (WP-0004) |
|
||||
| 11 | CI validation | `.gitea/workflows/ci.yml` | Closed (WP-0004) |
|
||||
| 12 | Registry federation | Cross-repo capability index composition | Open |
|
||||
|
||||
| Priority | Gap | Suggested outcome |
|
||||
|---|---|---|
|
||||
| 9 | Catalog site | Static browsable capability catalog (UC-RS-018) |
|
||||
| 10 | Overlap detection | CLI or report for duplicate/overlapping capabilities |
|
||||
| 11 | CI validation | Run `reuse-surface validate` in CI on registry changes |
|
||||
| 12 | Registry federation | Cross-repo capability index composition |
|
||||
| 13 | Interactive catalog | Searchable catalog UI beyond static HTML |
|
||||
| 14 | Graph visualization | Capability relation graphs |
|
||||
| 15 | Federation | Compose indexes across repositories |
|
||||
|
||||
---
|
||||
|
||||
@@ -289,4 +295,5 @@ own evidence (e.g. feature-control at R3).
|
||||
| Date | Change |
|
||||
|---|---|
|
||||
| 2026-06-15 | Initial analysis after REUSE-WP-0002 completion |
|
||||
| 2026-06-15 | REUSE-WP-0003 closed priority gaps 1–8; vector updated to D5/A3/C4/R2 |
|
||||
| 2026-06-15 | REUSE-WP-0003 closed priority gaps 1–8; vector updated to D5/A3/C4/R2 |
|
||||
| 2026-06-15 | REUSE-WP-0004 closed priorities 9–11 (catalog, overlaps, CI) |
|
||||
57
docs/catalog/index.html
Normal file
57
docs/catalog/index.html
Normal file
@@ -0,0 +1,57 @@
|
||||
<!DOCTYPE html>
|
||||
<html lang="en">
|
||||
<head>
|
||||
<meta charset="utf-8">
|
||||
<title>Capability Catalog — helix_forge</title>
|
||||
<style>
|
||||
body { font-family: system-ui, sans-serif; margin: 2rem; line-height: 1.5; }
|
||||
h1 { margin-bottom: 0.2rem; }
|
||||
.subtitle { color: #555; margin-bottom: 2rem; }
|
||||
section { margin-bottom: 2rem; }
|
||||
.card { border: 1px solid #ddd; border-radius: 8px; padding: 1rem; margin: 1rem 0; }
|
||||
.meta { color: #444; font-size: 0.95rem; }
|
||||
.path { font-size: 0.85rem; color: #666; }
|
||||
</style>
|
||||
</head>
|
||||
<body>
|
||||
<h1>Capability Catalog</h1>
|
||||
<p class="subtitle">Updated 2026-06-15 · 6 entries</p>
|
||||
<section><h2>helix_forge</h2>
|
||||
<article class="card">
|
||||
<h3>Feature Availability Evaluation</h3>
|
||||
<p class="meta"><code>capability.feature-control.evaluate</code> · D5 / A4 / C3 / R3</p>
|
||||
<p>Evaluate whether a feature is active, hidden, disabled, or unavailable for a subject in context.</p>
|
||||
<p class="path">registry/capabilities/capability.feature-control.evaluate.md</p>
|
||||
</article>
|
||||
<article class="card">
|
||||
<h3>Feature Rollout Control</h3>
|
||||
<p class="meta"><code>capability.feature-control.rollout</code> · D4 / A2 / C2 / R1</p>
|
||||
<p>Gradually expose features to subjects across tenants, domains, groups, or cohorts using rollout rules and staged availability.</p>
|
||||
<p class="path">registry/capabilities/capability.feature-control.rollout.md</p>
|
||||
</article>
|
||||
<article class="card">
|
||||
<h3>Identity Subject Resolution</h3>
|
||||
<p class="meta"><code>capability.identity.subject-resolution</code> · D3 / A0 / C1 / R0</p>
|
||||
<p>Resolve who or what is acting in a context by mapping principals, accounts, actors, and identifiers to a stable subject model.</p>
|
||||
<p class="path">registry/capabilities/capability.identity.subject-resolution.md</p>
|
||||
</article>
|
||||
<article class="card">
|
||||
<h3>Identity Vocabulary Canonicalization</h3>
|
||||
<p class="meta"><code>capability.identity.vocabulary-canonicalize</code> · D4 / A0 / C2 / R0</p>
|
||||
<p>Define and maintain an implementation-neutral vocabulary for identity-related concepts across overlapping domains.</p>
|
||||
<p class="path">registry/capabilities/capability.identity.vocabulary-canonicalize.md</p>
|
||||
</article>
|
||||
<article class="card">
|
||||
<h3>Capability Registration</h3>
|
||||
<p class="meta"><code>capability.registry.register</code> · D3 / A3 / C2 / R2</p>
|
||||
<p>Register a new capability so it becomes visible for planning and implementation reuse.</p>
|
||||
<p class="path">registry/capabilities/capability.registry.register.md</p>
|
||||
</article>
|
||||
<article class="card">
|
||||
<h3>Workstream And Task Coordination</h3>
|
||||
<p class="meta"><code>capability.statehub.workstream-coordinate</code> · D4 / A4 / C3 / R2</p>
|
||||
<p>Track active workstreams, tasks, progress, and consistency across domain repositories through a local-first coordination service.</p>
|
||||
<p class="path">registry/capabilities/capability.statehub.workstream-coordinate.md</p>
|
||||
</article></section>
|
||||
</body>
|
||||
</html>
|
||||
Reference in New Issue
Block a user