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

Complete WP-0006 through WP-0009: registry expansion, catalog, graph, tests
Some checks failed
ci / validate-registry (push) Has been cancelled
Details

Browse Source 
Register six new capabilities (12 total), add searchable catalog UI and graph
explorer, introduce pytest suite with CI fail-on-warnings, and close gap
analysis priorities 13 and 16. WP-0010 remains backlog for network federation.
This commit is contained in:
Bernd Worsch
2026-06-15 02:24:20 +02:00
parent 399690a5b6
commit e766f38e6f
30 changed files with 1632 additions and 80 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
docs/catalog/index.html
View File

@@ -15,8 +15,26 @@
</head>
<body>
<h1>Capability Catalog</h1>
<p class="subtitle">Updated 2026-06-15 · 6 entries</p>
<p class="subtitle">Updated 2026-06-15 · 12 entries</p>
<section><h2>helix_forge</h2>
<article class="card">
<h3>Organizational Event Coordination</h3>
<p class="meta"><code>capability.activity.event-coordinate</code> · D3 / A1 / C1 / R0</p>
<p>Coordinate structured responses to cross-domain events through activity workflows and automation.</p>
<p class="path">registry/capabilities/capability.activity.event-coordinate.md</p>
</article>
<article class="card">
<h3>Audit Event Retention</h3>
<p class="meta"><code>capability.audit.event-retain</code> · D4 / A2 / C2 / R1</p>
<p>Collect, normalize, retain, and search audit events with integrity evidence across tenants.</p>
<p class="path">registry/capabilities/capability.audit.event-retain.md</p>
</article>
<article class="card">
<h3>Authorization Policy Evaluation</h3>
<p class="meta"><code>capability.authorization.policy-evaluate</code> · D4 / A2 / C2 / R1</p>
<p>Evaluate access decisions from policy-as-code rules for subjects, resources, and actions.</p>
<p class="path">registry/capabilities/capability.authorization.policy-evaluate.md</p>
</article>
<article class="card">
<h3>Feature Availability Evaluation</h3>
<p class="meta"><code>capability.feature-control.evaluate</code> · D5 / A4 / C3 / R3</p>
@@ -26,19 +44,25 @@
<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>Gradually expose features to subjects across tenants, domains, groups, or cohorts using rollout rules.</p>
<p class="path">registry/capabilities/capability.feature-control.rollout.md</p>
</article>
<article class="card">
<h3>Feature Visibility Control</h3>
<p class="meta"><code>capability.feature-control.visibility</code> · D4 / A2 / C2 / R1</p>
<p>Control whether features are visible or hidden for subjects without changing entitlement or authorization.</p>
<p class="path">registry/capabilities/capability.feature-control.visibility.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>Resolve who or what is acting 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>Define 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">
@@ -47,10 +71,22 @@
<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>Registry Entry Validation</h3>
<p class="meta"><code>capability.registry.validate</code> · D4 / A3 / C3 / R2</p>
<p>Validate capability registry entries against schema, index consistency, and relation integrity.</p>
<p class="path">registry/capabilities/capability.registry.validate.md</p>
</article>
<article class="card">
<h3>Work Progress Logging</h3>
<p class="meta"><code>capability.statehub.progress-log</code> · D4 / A4 / C3 / R2</p>
<p>Record progress events, decisions, and session notes against workstreams and tasks in State Hub.</p>
<p class="path">registry/capabilities/capability.statehub.progress-log.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>Track active workstreams, tasks, progress, and consistency across domain repositories.</p>
<p class="path">registry/capabilities/capability.statehub.workstream-coordinate.md</p>
</article></section>
</body>