FJORD is an illustrative solid-oak table, not a customer. Withhold a mill record, claim the same timber twice, claim more units than were planned. The evaluator runs live in this browser; nothing leaves the device.
Open the FJORD dossier
Solid-oak dining table, unit 37 of 500, standing-forest entry in Denmark. The same profile-logic evaluator the published vectors drive. Illustrative throughout — never a customer, never a case study.
Sign in with Google or your e-mail — a link arrives, no password. Behind it: the desk bundle you chose to back up, its receipts, the map and the vault.
The bundle below is the desk's own export, synced to your account when you asked for it. Every state on it was derived on the desk by lib/dd.js from your records; this page draws it and adds nothing. The FJORD dossier under the tabs stays illustrative.
Illustrative SKU
FJORD · oak dining table
The light, what to do next, export. The scenarios below are the checks an auditor will try. Receipts and Map are the drill-down.
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.
◆
—
—
Every check row, itemised
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.
Where this unit sits in the full catalog
Highlighted chips are on this unit's path. Dashed chips exist in the catalog for chains that
need them — cooperatives, bonded warehouses, drop-ship, recovered wood — and stay out of your way until they
apply. Two entry branches exist; a unit takes one.
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 journey, on the globe
The same stations and arcs on a turning globe — the picture a phone films. Drawn by MapLibre GL, the engine GeoLibre is built on, from a coastline this site ships itself: no tile server, no third party, nothing fetched from anywhere but this origin, so it works offline like the rest of the portal. Positions are what the records declare, as above. The .geolibre.json the tools export is this same layer, so it opens in GeoLibre — and GeoLibre itself can now check a journey: install the OpenStamps plugin (Manage Plugins → install from URL) and paste a journey link into its panel; every stamp is checked inside GeoLibre with the released engine, and the result is shown in the plugin's panel. The map layers hold declared positions only, never a check result, and a saved project asks before it reads the journey again. For the other half of the picture — a stamp closing in real time — watch time close around a file.
Drag to turn, scroll to zoom, tap a station for its record. The globe stops turning when you touch it.
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.
Declared vs recomputed
Area recomputed on this device from the declared vertices with the same spherical
formula the farmer page seals. Above 4 ha, Art. 9 requires a polygon rather than a point — this plot
declares one.
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.