generated from coulomb/repo-seed
tegwick
e766f38e6f
Some checks failed
ci / validate-registry (push) Has been cancelled
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.
94 lines
4.8 KiB
HTML
94 lines
4.8 KiB
HTML
<!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 · 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>
|
|
<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.</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 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 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>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.</p>
|
|
<p class="path">registry/capabilities/capability.statehub.workstream-coordinate.md</p>
|
|
</article></section>
|
|
</body>
|
|
</html>
|