Products
Each product is the same sealed record read for one kind of decision. What you gain is not another dashboard: it is something to point at when the decision is questioned later, and a receipt anyone can check without asking us.
[unread] observations under all three ledger observed [unread]
Three products, one record
Every entry says what its buyer gets, then names the product and opens it. The receipt under each is one row from that product's own class, read when this page loaded.
For whoever prices against a competitor, buys from a supplier or answers for a listing. The value before and after every change, when the source said it and when we looked, sealed so the claim still holds a year later. A screenshot never carried the source's own clock, which is why this could not be shown before.
one receipt, read live [unread]
For whoever has to say whether an action was authorised, by whom and when. The standards the web runs on and the crawler registries beside them, read where they are published, with both clocks and a seal, so an action can be checked rather than believed. The rulebook changes without announcing itself, and until now its history went unkept.
one receipt, read live [unread]
For whoever has to prove what was issued and when it became visible. Each log's signed tree head, read at its operator with the log's own clock beside ours, and sealed. A certificate that validates today says nothing about the day in question, and the evidence you need is the evidence most likely to be gone.
one receipt, read live [unread]
The verbs
The same four on every surface. A product here is the record read for one decision, never a second machine.
Read the source as it is published, and write down both clocks.
Hash the row with its predecessor, so no receipt can move without every later one changing.
Fold the day's receipts into one root and put it where anyone can read it.
Submit the root to a chain we do not run. From then on, checking us does not involve us.