FA-74215 / Feature flag rollout bucketing / Member archive

Guarded progressive ramp: History lags one stage behind · case 05

Audit history shows the percentage before each advance, hiding when the ramp reached full traffic.

Member previewVariant 5 · 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
low-sample breach only holds	`[5, "ramping", [1, 1]]`	`[5, "ramping", [1, 5]]`	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.