Deriving verdicts from stored observations…

Books to Scrape — soumission 998

books.toscrape.com/…/index.htmllast run 2026-08-21 01:15liveplan v1 (seed)

Completedok3/3

Valueunverified

Extractiontrusted

Causehealthy

every run on one axis, oldest first · bar height is completeness, ink is the extraction verdict, a caret marks a run where the judges disagreed

How to read the four verdicts

Completed: How much of the extraction plan produced a value. Says nothing at all about whether the value is right.
Value: Whether the number is believable against this field’s own history. A price can be believable and still be the wrong price.
Extraction: Whether the place the value was read from has moved. This is the judge nothing else has, and the only one that catches a correct-looking number read from the wrong element.
Cause: What the evidence says is actually wrong — a redesign, a removed element, a real-world price change — and how confident that reading is.

Run history

Each run judged as it arrived. A marked row is one where the judges disagreed.

Recent runs, newest first, with all four verdicts.
Run	Completed	Value	Extraction	Cause	Plan
2026-08-21	ok3/3	unverified	trusted	healthy	v1

The evidence the verdicts above were derived from. Signals implying everything is fine are not listed.

availabilitytrusted0 comparisons

no-history
availability has no prior observations to judge this value against.
Nothing to do — this resolves itself as collection continues. It is reported so the value is not mistaken for a verified one.

pricetrusted0 comparisons