Files
feature-control/registry/capabilities/capability.feature-control.rollout.md
tegwick 82c7884103 Add capability registry scaffold and seed entries from reuse-surface
Bootstrap registry/indexes/capabilities.yaml and migrate helix_forge
capability entries owned by this repository for federation publishing.
2026-06-16 01:34:23 +02:00

3.1 KiB

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, evidence, consumer_guidance
id name summary owner status domain tags maturity external_evidence discovery availability relations evidence consumer_guidance
capability.feature-control.rollout Feature Rollout Control Gradually expose features to subjects across tenants, domains, groups, or cohorts using rollout rules and staged availability. feature-control draft helix_forge
feature-control
rollout
planning
discovery availability
current target confidence rationale
D4 D6 medium Rollout is a distinct bounded behavior from single-point evaluation, with research references in the feature-control domain and maturity standard.
current target confidence rationale
A2 A4 low Rollout logic may exist in source modules but is not yet consistently exposed as a standalone SDK or API surface distinct from evaluate.
completeness reliability
level name confidence basis satisfied_expectations broken_expectations out_of_scope_expectations
C2 Partial low scope_vs_intent_and_consumer_expectations
rollout concepts documented adjacent to feature evaluation
no dedicated rollout artifact called out separately from evaluate
percentage and cohort rollout variants not indexed independently
billing-driven entitlements
level name confidence basis known_reliability_risks
R1 Fragile low consumer_quality_signals
rollout behavior may be conflated with evaluate in consumer mental models
intent includes excludes assumptions use_cases research_memos
Control how features become available over time and across cohorts without conflating rollout policy with authorization or billing.
staged rollout rules
cohort and context targeting for rollout
explainable rollout state
one-time feature evaluation only
authorization decisions
billing entitlements
feature evaluation capability exists for final availability decisions
ucc.feature-control.domain-rollout
specs/CapabilityMaturityStandard.md
current_level target_level current_artifacts target_artifacts consumption_modes
A2 A4
feature-control/packages/feature-control-sdk
feature-control/services/feature-control-api
source module
SDK
depends_on supports related_to
capability.feature-control.evaluate
capability.feature-control.visibility
documentation tests consumer_feedback bug_reports incidents
specs/CapabilityMaturityStandard.md
recommended_for not_recommended_for known_limitations
planning staged feature exposure separate from binary evaluation
simple on/off evaluation without rollout semantics
entitlement or billing ownership
distinguish carefully from capability.feature-control.evaluate

Feature Rollout Control

Overview

Rollout governs how availability changes over time and across cohorts. It complements evaluation, which answers whether a feature is available for a subject in a context right now.