designesy
Score a site

designesy.org/monitor10 governance checks12 drift checks a runhistory in your browsercontract 0.1.5 provisional

Drift monitor

Track a URL for drift over time. Each run you start is kept as a snapshot in your browser and sent with the next run, which is compared with your first run and your last, so a regression shows up on the run it lands. Nothing is scheduled, and the server keeps no history of its own.

History stays in this browser.
Drift monitorwaiting for a URL10 checks · ready
The watch3

Earlier runs to compare against and a run on time. Alerts come back with the run.

The trend3

Where the score is heading across runs.

What changed4

Checks, tokens and contract since the last run.

Verdict

Run a URL and each governance check lights. The first run sets the baseline; later runs compare against it.

How a run works
First run m01 m03
Scores the page and stores the snapshot as the baseline.
Every run after m03 to m09
Compared with the baseline and the run before: score, trend, failures, tokens.
A drop past the threshold m07
Raises an alert, shown with the run.

Snapshots are stored in this browser only, 50 runs per URL.

  • pass
  • needs work
  • fail
  • does not apply
pass 1warn 0.5fail 0the grade measures the watch

Method

  1. Run the drift radar

    The same 12 checks as the drift radar, on the live page.

  2. Load your history

    Earlier snapshots of this URL, read from this browser and sent with the run.

  3. Compare

    Against the first run and the last: score, three-run trend, new failures, the token set and the contract version.

  4. Alert

    A drop past the threshold raises an alert, shown with the run.

governance = (pass + warn × 0.5) ÷ scored checks × 100A ≥ 90B ≥ 80C ≥ 70D ≥ 60F belowSnapshots stay in this browser: 50 runs per URL.

Next