We measure batch-level product carbon footprints, grade the evidence behind them and publish a register anyone can recompute. The certification conclusion is signed by an accredited partner; our job is the layer underneath that signature, and we say which layer we are on every page.
What we verify, how a label is frozen, what the register can prove, and what each of the four sectors gets out of it — in plain language.
Narrated overview. Every figure quoted is on this site: the register holds twenty modelled reference records, the chain is recomputable in your browser, and the method is published. Accreditation is still in progress, and the film says so.
70-second cut · vertical 9:16 · captions are burned in, so it reads with the sound off
Original score composed for this film. No licensed or library audio is used, and no attribution is required anywhere it is shown.
First cut 2026-11-06; re-cut 2026-11-07 so the narration and the register tile match the dataset (20 modelled reference records, live label verified separately).
None of them needs accreditation, because none of them is a certification conclusion. They are what makes a licensed partner's signature cheap to produce and hard to challenge.
One batch, one boundary, one ledger entry, one recomputable hash. Metred, bounded, attributed, committed, recomputable. Buyer pays ¥40–80 per batch; the grower pays nothing.
Read the standard →Plot, batch and container hashed together for the importer's due-diligence statement. ¥3,000–8,000 per container, or 0.2–0.5% of cargo value.
Read the pack →The same recomputable register, run under an accredited body's own brand. ¥30,000–100,000 per year plus ¥10–40 per batch.
Read the offer →Verification, assurance and advisory are different services with different liability. We only sell the first two, because selling the third to the same client invalidates both.
ISO 14067 verification of a single production batch: boundary, functional unit, emission factors, allocation rules and uncertainty, each re-derived rather than accepted.
Verification scope →Issuance of a hash-frozen label with a public registry entry. Anyone can recompute the hash in their own browser without trusting our server.
Label specification →Metrology traceability, sampling coverage and hash-chained records. We assure the evidence chain, not the accuracy of somebody's model.
Assurance scope →The stages and the end points are registered before any data is collected. That is what makes the result auditable rather than arguable.
Everything we rely on is written down with a version number and a challenge window. If a rule is wrong, the way to beat it is to submit a counter-example.
Thresholds derived from cost asymmetry, two-threshold triage, hard gates, abstention semantics. A method change ships a new version; old labels keep pointing at the old one.
Read the standard →Marginal grid intensity varies by hour. Scheduling load into the low-carbon window is the largest single lever on an aeroponic footprint — and it is measurable from the meter.
Read the method note →When the platform issues the label, sells the premium and takes the insurance split, its numbers stop being evidence. Structural separation is the product.
How we are structured →Scoping is free. If the data will not support a defensible label, you will hear that before you pay for anything.