Flag Removal Map

FIELD NOTE 01 / FEATURE-FLAG DEBT

Survey every trace before you remove the flag.

Join provider state, bounded evaluation evidence, and literal references across your repositories. Get a reviewable cleanup route—not a false promise that “zero” means safe.

Install the CLI Run the field demo
  • Offline
  • Read-only
  • No telemetry
  • MIT
An abstract topographic repository map with three evidence markers joined by a red survey route.
47° CODE3 evidence stationsRoute requires review
  1. 01
    InventoryRead provider export
  2. 02
    Cross-checkJoin activity + references
  3. 03
    RouteWrite the removal plan
THE TERRAIN

Creation date is not removal evidence.

Provider dashboards can tell you that a flag looks stale. Repository search can tell you where a key appears. Neither alone tells a small team whether the cleanup route is complete.

“No evaluations observed” is a clue. It is never proof that a code path is dead.

Built-in safety rule
FIELD DEMO / LOCAL ONLY

Plot one flag before touching code.

Change the offline sample inputs and see the same decision rule the CLI applies. Nothing leaves this browser.

One normalized flag object.
Zero needs a bounded observation window.
Paste file-name and source lines for this browser demo; the CLI scans real directories.

Evidence station ready

Run the survey to classify the flag and map its visible references.

PACK THE KIT

One binary. Offline inputs. Reviewable output.

Build from source today. Release binaries can be dropped into any CI job without a service account or network dependency.

cargo install --git https://github.com/B-Divyesh/sf-flag-removal-map 
flag-removal-map \
  --flags ./flags.json \
  --evaluations ./evaluations.json \
  --repo ./apps --repo ./packages \
  --out ./flag-removal-plan.md

Map legend

Keep
Active provider state or observed evaluations.
Remove
Completed state plus bounded zero evidence. Still human-reviewed.
Review
Missing, contradictory, or incomplete evidence.
KNOWN BOUNDARIES

Conservative by design.