LEDGERMACHINE

LM-LAYER-001

Find conflicting CSS cascade-layer values

The same selector and property receive different values in more than one named layer.

What Ledgermachine reports

A property changes between cascade layers

Decision, not automatic repair

Confirm which layer owns the final value and remove declarations that no longer have a distinct purpose.

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
@layer components { .button { color: var(--ink); } }
@layer overrides { .button { color: #222; } }
One possible resolution
@layer components {
  .button { color: var(--ink); }
}

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

    Confirm which layer owns the final value and remove declarations that no longer have a distinct purpose.

  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