levelfield Sign in

Things that look broken but are not

Most of what will worry you is this system correctly staying quiet. Silence is the hardest thing to interpret, so every one of these is listed here in one place.

A brand-new company with no findings

Every rule needs weeks of real watching before it can speak. The shortest minimum is seven days in a row, the longest is fourteen separate days inside ninety. No findings on day three is the product refusing to accuse anyone after one look, not the product failing.

An empty walks list

Checkout walks happen once a week at most, and only after a daily visit has recorded a price. A fresh company shows nothing for a day or two.

A walk that stopped at the first screen

The walker stops the moment it is unsure, and some ordinary product pages trigger that. Stopping is the safe direction, and the walk's own page names exactly what ended it.

Every walk saying "stopped"

That is a list of successes. The walker halting rather than buying is the entire safety design. A walk that did NOT stop would be the thing to worry about.

A walk you cannot run yet

Walks are limited to one a week per shop, and a failed walk counts against that limit exactly like a successful one, because it still visited the shop and may still have added to its cart.

A finding with no money figure

Either no revenue figure has been recorded for that company, or the evidence is too thin to print an honest number. A missing figure always means "not known". It never means "nothing at stake".

An empty claims list

Pages are read only when their wording changes, and only after they have been captured, so a company added recently shows nothing for a day or two. An empty list means we have not looked yet, never that the company makes no claims.

A claim the reading threw away

The reading may only quote. Every quote is checked against the saved page character by character, and anything not found exactly is discarded before it reaches anything else. A discarded quote is the safety design working, not a fault.

A fee finding that never appeared

Before a hidden-fee finding opens, the pictures on that product page are checked to see whether the fee was named there after all. A fee disclosed only inside a banner image reads to a text-only reading exactly like a fee that was never mentioned, so a finding suppressed that way is a wrong flag avoided.

The assistant holding sentences back

Every sentence it writes must point at a specific record we hold, and must not read as a legal conclusion. Sentences failing either check are deleted before you see them, and you are always told how many. Silence never hides a deletion.

Nothing read because no model key is set

The reading and looking engines need a model key. Without one they skip and say so, and nothing is lost: pages are read only when their wording changes, so they are read on the first run after a key is added.

A customer who says they paid and sees nothing

Almost always the order has not been marked paid yet. Open Customers and press "mark the invoice paid".

A price that says "not read"

We refuse to guess a currency. A page showing a bare dollar sign with nothing saying which country's dollars records the price as unread, with the reason, rather than storing a possibly wrong number that would end up in a legal document.

A run that says "saved pages but no prices"

The pages saved fine but no price could be read on any of them. Usually the currency setting, occasionally a shop that draws prices in a way our reader does not recognise. The discount rules cannot speak while that is true, and the run says so rather than looking clean.

A company marked as turning us away

Some sites block automated visits. We do not disguise the browser and we never answer human-verification challenges, so a site that blocks us stays unwatched. A block page is recorded as a failed visit and is never filed as evidence.