designesy.org/monitor10 governance checks12 drift checks a runhistory in your browsercontract 0.1.3 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.
Earlier runs to compare against, a run on time, and alerts that can reach you.
Where the score is heading across runs.
Checks, tokens and contract since the last run.
Run a URL and each governance check lights. The first run sets the baseline; later runs compare against it.
- 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 m10
- Raises an alert, mailed to you if you left an address.
Snapshots are stored in this browser only, 50 runs per URL.
- pass
- needs work
- fail
- does not apply
Method
Run the drift radar
The same 12 checks as the drift radar, on the live page.
Load your history
Earlier snapshots of this URL, read from this browser and sent with the run.
Compare
Against the first run and the last: score, three-run trend, new failures, the token set and the contract version.
Alert
A drop past the threshold raises an alert, mailed to the address you left, at most once an hour.
governance = (pass + warn × 0.5) ÷ 10 × 100A ≥ 90B ≥ 80C ≥ 70D ≥ 60F belowSnapshots stay in this browser: 50 runs per URL.