A shipped code path may be hidden, exposed to a small group, compared against another experience, or turned off during an incident. Those are different decisions. This track follows a case-review interface whose new assignment panel is released in stages. It covers stable evaluation, safe defaults, server enforcement, experiment exposure, metric integrity, and flag retirement. Every flag has an owner and an expiry plan; none grants data permission. The examples are compact decision checks, while real evaluation and measurement require an audited service and deployment path.
Topics in this track
- Feature Flag Evaluation Scope and Safe Default — Evaluate a named release decision consistently without using it as a data-permission check.
- Gradual Rollout, Kill Switch, and State Compatibility — Expose a release in stages and prove disabling it leaves stored data and sessions usable.
- Experiment Assignment, Exposure, and Metric Integrity — Keep variant assignment, actual exposure, and outcome measurement separate and comparable.
- Flag Telemetry, Audit, and Retirement — Record enough decision evidence to debug a release, then remove temporary branches and rules.
Prerequisite paths
Release checks: prove the critical route and prepare a rollback; Production Signals and Incident Decisions.
Neighbor track
GraphQL Query and Resolver Boundaries.
Practice path
Build Project: assignment panel release experiment and check decisions in Web Development: release and GraphQL decisions quiz.
Further connections
Capability Rollout and Fallback Retirement.