LEDGERMACHINE

LM-DRIFT-003

Detect declining design-token coverage

Static token coverage drops by at least five percentage points from the comparison scan.

What Ledgermachine reports

Fewer declarations use tokens than before

Decision, not automatic repair

Inspect the new direct values and restore token use where the bypass was not deliberate.

Source example

What this finding can look like

The exact candidate comes from the project’s own tokens and repeated values. This example shows the shape of the issue, not a universal replacement.

Flagged source
.new-card { color: #1a1a1a; padding: 15px; }
One possible resolution
.new-card { color: var(--ink); padding: var(--space-4); }

Resolution workflow

Fix the source without erasing intent

  1. Inspect

    Review every reported occurrence and the established candidates Ledgermachine found in the same project.

  2. Decide

    Inspect the new direct values and restore token use where the bypass was not deliberate.

  3. Verify

    Make the change in your editor or coding agent, then rescan. Ledgermachine stays read-only and records whether the finding cleared.

Run it on your source

See the evidence behind this rule.

Open a folder locally, inspect the exact occurrences, and decide whether to repair or preserve the difference.

Open Ledgermachine