| capability.feature-control.visibility |
Feature Visibility Control |
Control whether features are visible or hidden for subjects without changing underlying entitlement or authorization. |
feature-control |
draft |
helix_forge |
| feature-control |
| visibility |
|
| discovery |
availability |
| current |
target |
confidence |
rationale |
| D4 |
D5 |
medium |
Bounded as distinct from evaluation and rollout in feature-control domain. |
|
| current |
target |
confidence |
rationale |
| A2 |
A4 |
low |
May share SDK artifacts with evaluate but is not separately exposed as API. |
|
|
| completeness |
reliability |
| level |
name |
confidence |
basis |
satisfied_expectations |
broken_expectations |
out_of_scope_expectations |
| C2 |
Partial |
low |
scope_vs_intent_and_consumer_expectations |
| visibility distinguished from evaluation in registry model |
|
| no standalone visibility API documented separately |
|
| authorization policy decisions |
|
|
| level |
confidence |
basis |
known_reliability_risks |
| R1 |
low |
consumer_quality_signals |
| easily conflated with evaluate capability |
|
|
|
| intent |
includes |
excludes |
use_cases |
| Govern feature visibility separately from availability evaluation and rollout staging. |
| hide/show feature UI or capability surfaces |
| visibility rules per subject context |
|
| entitlement ownership |
| rollout percentage control |
|
|
|
| current_level |
target_level |
current_artifacts |
consumption_modes |
| A2 |
A4 |
| feature-control/packages/feature-control-sdk |
|
|
|
| depends_on |
related_to |
| capability.feature-control.evaluate |
|
| capability.feature-control.rollout |
|
|
| recommended_for |
not_recommended_for |
known_limitations |
| planning visibility behavior separate from on/off evaluation |
|
| authorization or billing gating |
|
| implementation may be bundled with evaluate SDK today |
|
|