coulomb/reuse-surface
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Complete REUSE-WP-0004: CI, overlap detection, and catalog generation
Some checks failed
ci / validate-registry (push) Has been cancelled
Details

Browse Source 
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:
Bernd Worsch
2026-06-15 01:20:31 +02:00
parent 5c5023c000
commit c366fc4a4e
12 changed files with 538 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
docs/catalog/index.html Normal file
View 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>