We verify batch-level product carbon footprints and issue the labels that let agricultural goods cross borders under scope 3 rules. Independent of the software, the hardware and the seller — that is the only reason a buyer should accept our signature.
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.