Attack an illustrative dossier.

Every receipt on this unit

Drill-down from Today. This unit commits — events (typical is 8–15). Only S32 mints per unit. Use the scenario buttons to withhold a mill upload or double-count timber.

This unit's receipts — chained

Each receipt below commits the digest of the one before it, recomputed live in this browser (SHA-256 over the committed record plus the previous link). Alter any byte upstream and every later link changes. These are illustrative receipts hashed on this page — they carry no CSTP envelope, signature or resolved anchor, so their time brackets draw open at both ends; the format underneath is demonstrated on the stamp tool. The records were written before the osp/furniture/1 vocabulary of 2026-09-04; this page lifts them to it once (class, unit factor, seal and permit commitments, the supplier commitment without its salt) and evaluates the lifted bytes — what you see hashed is what was judged.

The journey, on a map

The same map the chain reader draws: where each record declares it happened, the plot ring from the sealed bytes, and an arc for every parent citation. In this illustration only the S49 plot polygon is a committed, hashed field — the other positions and dates are display metadata standing in for fields a production deployment seals into each receipt. Sealing fixes the bytes; it does not by itself prove the reading was honest. The glyph beside each station is the evaluator's own row for it under the active scenario. Drag to pan, Ctrl+scroll or the buttons to zoom, tap a station for its receipt.

The plot, inspected

The declared S49 polygon — the geolocation field EUDR Art. 9 names — on a real map. Tiles are off until you switch them on (the same per-session choice as the chain map above). The evaluator's own row for this field is shown beside it, not a caption written in advance.

Receipt vault — on this device, exportable

The vault is this browser's storage on this machine: receipts stay yours and stay local. The export bundle is your backup — download it after a session and keep it with the dossier; the chain re-check runs offline from the bytes alone. Nothing is replicated to a server, and the format stays checkable if this company is gone.

Browser storage can be evicted by the operating system under disk pressure. The bundle you export is the durable copy — treat the vault as a working set, not the archive.