CorbelworksUTILITY & TELECOM RECOVERY

Disclosure

How this site learns

This site measures which sections readers actually engage with, and reorders parts of itself accordingly. That is a mild form of surveillance and it deserves a plain explanation rather than a paragraph buried in a privacy policy.

The loop, in four steps

  1. Sense. A small script notes how long each labelled section was on screen, how far down the page you scrolled, which calculators you ran, and whether you are on a phone or a desktop.
  2. Aggregate. That bounded summary is sent to our edge and stored as counts and durations under a random identifier your browser generates. It expires after ninety days.
  3. Rank. Across all sessions in a rolling thirty-day window, sections are scored by attention: seconds on screen, plus a weighting for actually running a calculator, because using something means more than looking at it.
  4. Adapt. The calculators and defect cards reorder so that whatever readers genuinely engage with rises to the top. When a block has been reordered, the page says so underneath it.
Inspect it yourself

The entire aggregate that drives the reordering is public: /api/ranking. Sample size, attention seconds per section, interaction counts, and the resulting scores. If we are going to measure readers, the readers get to see the ledger.

What is measured

SignalFormWhy
Section dwellMilliseconds a labelled block was ≥40% on screenTells us which explanations are doing work and which are being scrolled past
Scroll depthFurthest percentage of the page reachedDistinguishes "read it" from "landed and left"
Named actionsCounts, e.g. calc_sewer, cta_emailWhich tools get used, which links get taken
Route visitsVisit count and active time per page pathWhich pages carry the load
Viewport / pointerOne of mobile, tablet, desktop / touch, mouseLayout decisions
CountryTwo-letter code from the edgeWhether we are reaching the market we think we are

What is never measured

How to opt out

The script honours the browser's Do Not Track setting and does nothing at all when it is enabled. Clearing site data for this domain deletes the local aggregate and issues a new random identifier on your next visit. Blocking /assets/sensorium.js disables the whole thing; every page works normally without it, including the calculators.

Why build this at all

We ask operators to trust a written finding about their own invoices. A firm that measures its readers without saying so, or that claims it collects nothing while running three trackers, has already answered the question of how it handles inconvenient facts.

So this page exists as much for what it demonstrates as for what it discloses: state the mechanism, publish the ledger, and let the reader check. That is the same standard we hold our findings memos to — every claim carries the tariff section that supports it, so you can verify rather than trust.

The honest limit

Cloudflare, which serves this site, keeps its own edge request logs including IP addresses, as any host does. That is outside the system described here and we cannot claim otherwise. What we control is what we collect, store, and act on — and that is the list above and nothing else.

Current aggregate: /api/ranking · Live news sources: /api/rate-watch · Signing key: /provenance-public-key.json