FA-74217 / Feature flag rollout bucketing / Member archive

Guarded progressive ramp: Rolled-back ramps report their last stage · case 02

The summary claims the feature is still at 25 percent after it was rolled back.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

stages is an increasing list of percentages; the ramp starts at stages[0]. Each check [error_rate, sample] is processed in order: after a rollback everything stays at 0; a sample below 100 holds the current stage; an error rate above 0.02 rolls back to 0 permanently; otherwise advance one stage (staying at the last). State is complete at the last stage, rolled_back after a rollback, else ramping. Return [final percent, state, percent after each check].

Why this case matters

Automated ramps with guardrails must neither overreact to noise nor resume after a rollback.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
rollback is terminal	`[1, "rolled_back", [0, 0, 0]]`	`[0, "rolled_back", [0, 0, 0]]`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.