reuse-surface/docs/CapabilityCatalog.md

Capability Catalog

Domain: helix_forge
Updated: 2026-06-15
Entries: 20

Generated by reuse-surface catalog. Do not edit manually.

helix_forge

Organizational Event Coordination

• ID: capability.activity.event-coordinate
• Vector: D3 / A1 / C1 / R0
• Owner: activity-core
• Path: registry/capabilities/capability.activity.event-coordinate.md
• Summary: Coordinate structured responses to cross-domain events through activity workflows and automation.

Known limitations:

• early discovery stage

Audit Event Retention

• ID: capability.audit.event-retain
• Vector: D4 / A2 / C2 / R1
• Owner: audit-core
• Path: registry/capabilities/capability.audit.event-retain.md
• Summary: Collect, normalize, retain, and search audit events with integrity evidence across tenants.

Known limitations:

• consumer evidence not yet collected in registry

Authorization Policy Evaluation

• ID: capability.authorization.policy-evaluate
• Vector: D4 / A2 / C2 / R1
• Owner: flex-auth
• Path: registry/capabilities/capability.authorization.policy-evaluate.md
• Summary: Evaluate access decisions from policy-as-code rules for subjects, resources, and actions.

Known limitations:

• maturity evidence is registry-external today

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.

Known limitations:

• distinguish carefully from capability.feature-control.evaluate

Feature Visibility Control

• ID: capability.feature-control.visibility
• Vector: D4 / A2 / C2 / R1
• Owner: feature-control
• Path: registry/capabilities/capability.feature-control.visibility.md
• Summary: Control whether features are visible or hidden for subjects without changing entitlement or authorization.

Known limitations:

• implementation may be bundled with evaluate SDK today

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 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 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 / A4 / 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

Registry Entry Validation

• ID: capability.registry.validate
• Vector: D4 / A3 / C3 / R2
• Owner: reuse-surface
• Path: registry/capabilities/capability.registry.validate.md
• Summary: Validate capability registry entries against schema, index consistency, and relation integrity.

Known limitations:

• warnings do not fail CI unless --fail-on-warnings is set

Work Progress Logging

• ID: capability.statehub.progress-log
• Vector: D4 / A4 / C3 / R2
• Owner: state-hub
• Path: registry/capabilities/capability.statehub.progress-log.md
• Summary: Record progress events, decisions, and session notes against workstreams and tasks in State Hub.

Known limitations:

• hub must be running locally or via tunnel

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.

Known limitations:

• requires running State Hub locally or via tunnel

Capability-Aware Shard Adapter Contract

• ID: capability.wiki.adapter-contract
• Vector: D5 / A2 / C2 / R1
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.adapter-contract.md
• Summary: A versioned backend interface where each binding declares a verified capability profile, so federation ops degrade by capability.

Known limitations:

• reference implementation covers the file-store substrate only so far

Event-Sourced Coordination Journal

• ID: capability.wiki.coordination-journal
• Vector: D5 / A2 / C2 / R1
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.coordination-journal.md
• Summary: An append-only, totally-ordered-per-space decision log whose current state is a derived fold; git-addressable history.

Known limitations:

• production git backing + lease are still on the roadmap (SHARD-WP-0009)

Wiki Derived Views

• ID: capability.wiki.derived-views
• Vector: D3 / A0 / C0 / R0
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.derived-views.md
• Summary: Recomputable views over a wiki union — BackLinks, RecentChanges, AllPages, SiteMap, and (delegate-or-derive) Search — carrying provenance.

Known limitations:

• not implemented; Search ranking policy undecided

Wiki Engine with Typed Extensions

• ID: capability.wiki.engine-typed-extensions
• Vector: D3 / A0 / C0 / R0
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.engine-typed-extensions.md
• Summary: A small-core wiki engine realizing a typed-extension framework that addresses all wiki use cases and lets each shard activate only the features it needs.

Known limitations:

• architecture authored; extension SDK/ABI + API protocol still to design; not yet built

Selectable Federation-Model Taxonomy

• ID: capability.wiki.federation-models
• Vector: D4 / A0 / C1 / R0
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.federation-models.md
• Summary: Federation as a plural, composable coordination axis (fork+journal, VCS-replication, query-join, feed, activity-streams, engine-mirror) selected per space.

Known limitations:

• no transport implemented; informational planning reuse only

Overlay-Before-Mutation Write Path

• ID: capability.wiki.overlay
• Vector: D5 / A2 / C2 / R1
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.overlay.md
• Summary: Non-destructive edits (draft -> patch -> apply-under-drift) that let read-only or limited backends be edited safely without silent remote mutation.

Known limitations:

• merge is detect-and-refuse; three-way merge is future work

Backend-Neutral Wiki Page Model

• ID: capability.wiki.page-model
• Vector: D5 / A2 / C2 / R1
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.page-model.md
• Summary: A Markdown-first but stretchable page model with stable identity separate from placement and layered provenance.

Known limitations:

• non-prose shapes specified ahead of implementation

Wiki Shard Orchestration

• ID: capability.wiki.shard-orchestration
• Vector: D5 / A2 / C2 / R1
• Owner: shard-wiki
• Path: registry/capabilities/capability.wiki.shard-orchestration.md
• Summary: Present a union of pages across heterogeneous wiki-shaped shards while preserving each shard's provenance, capabilities, and history.

Known limitations:

• resolution is recompute-on-read until the incremental tier lands