Files
reuse-surface/registry/capabilities/capability.feature-control.visibility.md
tegwick e766f38e6f
Some checks failed
ci / validate-registry (push) Has been cancelled
Complete WP-0006 through WP-0009: registry expansion, catalog, graph, tests
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.
2026-06-15 02:24:20 +02:00

2.1 KiB

id, name, summary, owner, status, domain, tags, maturity, external_evidence, discovery, availability, relations, consumer_guidance
id name summary owner status domain tags maturity external_evidence discovery availability relations consumer_guidance
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
source module
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

Feature Visibility Control

Visibility governs whether a feature surface appears, distinct from whether the feature is enabled for a subject.