Corobate

Exemplary Scenario

A $4.2M order, four tiers deep, on evidence that isn't there

A fully worked illustration: sparse data from a long-tail supply chain, a stale audit, and an AI summary that invented a certificate number — and the receipt that turned all of it into a documented, reconstructable decision.

Exemplary — illustrative only Every organization, person, supplier, certificate number, document reference, date and dollar figure on this page is fictional and constructed for illustration. No real company, product batch, laboratory, certification body or transaction is depicted. The regulatory obligations referenced (EU Regulation 2023/1542 on batteries, and its Digital Product Passport requirements) are real; their application to any actual transaction depends on facts not present here. The figures are modeled to be internally consistent and plausible, not measured.

What's on this page

  1. The decision, the people, the deadline
  2. Three ways the evidence fails: sparse, stale, hallucinated
  3. Day 0 — the receipt that says no
  4. Hold, fold, or go: how the branch is chosen
  5. Day 9 — the receipt that says yes, with conditions
  6. What the other path would have cost
  7. The evidentiary test: six questions a reviewer asks
  8. Day 180 — the backtest that changes the rules

01The decision, the people, the deadline

ElementDetail
Buying organizationMeridian Grid Systems, Inc. — a grid-scale battery storage integrator
Decision ownerDana Okoro, Senior Manager, Cell & Module Sourcing
actor:human:dokoro@meridiangrid.example
The decisionRelease purchase order PO-2026-4417: 3,000 LFP traction-grade modules at $1,400 each — $4,200,000
Tier-1 supplierVoltCore Energy GmbH, Leipzig · actor:org:VOLTCORE-DE-8812 · batch LFP-2026-Q2-7741
End useA 42 MWh storage installation for a utility customer in Ireland, commissioning window opens November 2026
Regulatory contextEU Regulation 2023/1542 — a Battery Digital Product Passport must accompany the units, including carbon footprint declaration, due-diligence disclosure on cobalt and graphite, and battery-management state-of-health data access
Hard deadline21 July 2026. Miss it and the November commissioning slot goes to another project — a six-week slip
Schedule float14 days
Decision date7 July 2026, 14:33 UTC

The long tail. Dana has a contract with VoltCore and with nobody else. The modules contain cells from a tier-2 contract manufacturer, whose cathode active material comes from a tier-3 processor, whose cobalt comes from a tier-4 refiner Dana cannot name. Four tiers, one contractual relationship. Every claim about the bottom two tiers arrives as a claim about a claim.

02Three ways the evidence fails

Seven facts have to hold for the passport to be compliance-grade. Here they are on 7 July, as they actually stand.

#Required factDeclared valueBackingClassReliabilityCritical?
1Carbon footprint58.4 kg CO₂e/kWhISO 14067 verification, cert CFV-2026-1188, resolved in issuer register 7 Julverified0.94yes
2Hazardous substancesPb <0.004%, Cd <0.001%, Hg n/dAccredited lab LAB-DE-0447, report TR-88214, 19 May 2026verified0.96yes
3Cobalt origin100% responsibly sourcedBook-and-claim mass balance allocation. No physical traceability. Tier-4 refiner not identifiedmodeled0.72yes
4Recycled content16%Supplier declaration referencing an audit dated Dec 2024 — 19 months oldseller-asserted0.45no
5Cycle life6,000 cycles @ 80% DoDDatasheet rev 3.2, supplier test protocolseller-asserted0.50no
6State-of-health algorithm disclosureNothing supplied. Required for BMS data accessmissing0.00yes
7Renewable energy share in manufacturingNothing supplied.missing0.00yes

Sparse — row 3

Nobody is lying. A book-and-claim allocation is a legitimate instrument. It just doesn't establish that these cells contain that cobalt. The evidence exists; it answers a different question than the one being asked. Class: modeled, not verified.

Stale — row 4

A real audit, honestly reported, 19 months out of date. Two production line changes have happened since. The number may still be right. It is no longer known to be right, and the freshness rule caps it accordingly.

Hallucinated — the paragraph that nearly shipped the order

On 5 July, Meridian's sourcing copilot — an LLM with access to the supplier document store — produced this in its pre-award summary:

// sourcing-copilot/v4 · pre-award supplier summary · 2026-07-05T09:41Z
"VoltCore's LFP-54 modules carry third-party verified 16% recycled content
 under ISO 14067 conformance, certificate CFV-2026-1204, and disclose BMS
 state-of-health parameters per Regulation (EU) 2023/1542 Article 14."

It is fluent. It is correctly formatted. It cites a regulation that exists, an article that exists, and a certificate number that looks exactly like the real one. It is wrong in three separate ways:

The claimThe reality
"third-party verified 16% recycled content"The 16% is a supplier declaration. No third party verified it. The word "verified" was generated, not sourced.
"certificate CFV-2026-1204"Does not resolve in the issuer's register. The real certificate is CFV-2026-1188 — one field off — and it covers carbon footprint, not recycled content.
"disclose BMS state-of-health parameters"No such disclosure exists. It had been requested and never delivered.

Why this is the dangerous one Sparse and stale data announce themselves — a careful reader sees the gap. A hallucination does the opposite: it closes the gap in the reader's mind. Dana's file, read quickly, now appears to contain third-party verification and a compliant BMS disclosure. Nothing in the summary looks uncertain. This is precisely the failure mode where a person exercising ordinary care still ends up releasing the order.

03Day 0 — the receipt that says no

7 July 2026, 14:33 UTC. The seven fields go into the engine. Nothing is skipped.

Step 1 — resolve the AI's citation before it can earn anythingregister_lookup( "CFV-2026-1204" ) → NOT_FOUND
→ input class capped at MODELED; reason recorded: ai_citation_unresolved
→ recycled_content remains seller-asserted at 0.45
Step 2 — gate on the sufficiency-critical subset {1, 2, 3, 6, 7}confidence = min( 0.94, 0.96, 0.72, 0.00, 0.00 ) = 0.00
bound_by = soh_algorithm_disclosure
SEALED RECEIPT · dcn_dpp_LFP-2026-Q2-7741 · engine corobate 1.4.2 · weight_version wv-2026-01
QuestionIs batch LFP-2026-Q2-7741 passport-sufficient to release PO-2026-4417?
Verdictwithheld
Confidence0.00 · bound_by soh_algorithm_disclosure
coverage_gapssoh_algorithm_disclosure · renewable_energy_share_manufacturing
seller_assertedrecycled_content · cycle_life
abstention_reasoncritical_input_absent
notesai_citation_unresolved: CFV-2026-1204 (actor:ai:sourcing-copilot/v4)
data_horizon2026-07-07T14:30:00Z · no input after this time admitted
receipt_hash sha256:539c1503… · chained · RFC 3161 anchored 2026-07-07T14:33:11Z · demo token · re-runnable ✓

The receipt does not say "risky." It says which field, why, and what would clear it. That converts directly into an evidence request:

// Evidence request ER-4417-01 · to VoltCore Energy GmbH · 7 Jul 2026 · due 17 Jul 2026
Referencing receipt sha256:539c1503…

1. soh_algorithm_disclosure   — BMS state-of-health parameter set + firmware
                                interface spec. Clears at VERIFIED on
                                independent confirmation against shipped firmware.
2. renewable_energy_share_    — Grid supply attestation for the Leipzig line,
   manufacturing                with guarantees of origin. Clears at VERIFIED.
3. material_origin_cobalt     — Physical traceability documentation to the
                                refiner, if it exists. Currently modeled (0.72)
                                on a book-and-claim allocation.

Note: certificate CFV-2026-1204, referenced in our pre-award summary, does not
resolve in the issuer register. Please confirm CFV-2026-1188 scope.

04Hold, fold, or go: how the branch is chosen

WITHHELD is not automatically "walk away." The receipt tells you the verdict; obtainability tells you the action.

BranchTriggerAction takenWhat is documented
hold — abstainThe missing evidence exists and the counterparty can produce it. Schedule float (14 days) can absorb the wait.Chosen. PO held. ER-4417-01 issued with a 10-day deadline. Alternate supplier put on standby, not engaged.Receipt #1, the evidence request keyed to its hash, and the standby decision — all timestamped before the answer came back.
fold — walk awayVoltCore declines to disclose the SoH parameters, or the deadline passes.Not taken here. Would have triggered: re-source to the qualified alternate, six-week slip, customer notification.The refusal itself would enter as a dated, seller-asserted input, and receipt #1 would stand as the record of what was asked and when.
go, with conditionsGaps close but the weakest critical input remains modeled or seller-asserted.Taken on day 9. See below.Receipt #2 with the named residual weakness, plus the commercial conditions attached to it.
go forwardAll critical inputs independently backed.Not reached in this scenario — the cobalt claim never became physically traceable.Would require receipt #3 at ≥0.80.

05Day 9 — the receipt that says yes, with conditions

16 July 2026. VoltCore delivers two of the three items.

FieldWhat arrivedNew classNew reliability
soh_algorithm_disclosureBMS parameter set + firmware interface spec, confirmed by Meridian's own controls engineer against the shipped firmware buildverified0.95
renewable_energy_share_manufacturing87% — Leipzig line grid supply attestation with guarantees of originverified0.95
material_origin_cobaltNothing further. Physical traceability to the refiner does not exist for this batchmodeled0.72 (unchanged)
Re-gate on the same critical subsetconfidence = min( 0.94, 0.96, 0.72, 0.95, 0.95 ) = 0.72
bound_by = material_origin_cobalt  →  0.72 ≥ 0.50 and < 0.80  →  caution
SEALED RECEIPT · dcn_dpp_LFP-2026-Q2-7741-r2 · engine corobate 1.4.2 · weight_version wv-2026-01
Verdictcaution
Confidence0.72 · bound_by material_origin_cobalt
Qualified opinioncobalt origin established by mass-balance allocation, not physical traceability
coverage_gapsnone
prior_entrysha256:539c1503… (receipt #1)
chained to receipt #1 · RFC 3161 anchored 2026-07-16T11:08:44Z · demo token · re-runnable ✓

Decision: go forward, with conditions. PO-2026-4417 released 17 July — four days of float remaining, November slot held. The CAUTION verdict is not a warning that gets filed away; it is the source of four specific commercial terms:

ConditionDirectly traceable to
15% payment holdback — $630,000 — released on delivery of physical traceability documentationbound_by: material_origin_cobalt
Contractual representation naming cobalt origin specifically, with a defined remedyThe qualified opinion text
Incoming inspection extended: cobalt content spot assay on 2% of modulesThe modeled-not-measured character of the claim
Both receipts attached to the DPP record and to the customer's compliance fileThe passport obligation itself

Cost of the nine-day hold: $18,000 in re-planned inbound logistics. No expedite premium — the hold fit inside the float.

06What the other path would have cost

Suppose the copilot's paragraph had gone unchallenged and the PO released on 7 July.

ConsequenceExemplary cost
Missing SoH disclosure surfaces at conformity assessment; shipment held pending passport completion21-day commissioning delay
Liquidated damages under the utility contract at $9,500/day$199,500
Module relabeling, retest, and passport remediation$86,000
Internal legal time and evidence reconstruction — assembling, after the fact, what was known on 7 July$40,000
Total exemplary exposure$325,500
And the part that isn't a dollar figure: no contemporaneous record of what was known, what was asked, or why the order was released. The only artifact would be an AI-generated paragraph asserting a certificate that does not exist — in the file, unattributed, indistinguishable from evidence.

Against $18,000 for the hold. The ratio is roughly 18:1 — but the ratio is the smaller point. The larger one is that the $18,000 was a decision, made deliberately, on a documented basis, and the $325,500 would have been an accident.

07The evidentiary test: six questions a reviewer asks

Whether the reviewer is an internal auditor, a customer's compliance team, a notified body, an insurer, or opposing counsel, the questions converge.

The questionWhat a conventional file offersWhat the receipt offers
What did you actually know on 7 July?Email threads, a shared drive, and someone's recollection. Documents added later are indistinguishable from documents present at the time.Every input with its own observed_at, and a sealed data_horizon that rejected anything dated after 14:30 UTC. Nothing from later can be in there.
Did you rely on the AI summary?Usually unanswerable. The summary was pasted into a document and lost its origin.Yes — admitted as modeled with the model id and prompt hash, and its unresolvable citation flagged by name.
Did you ask for what was missing?Perhaps a saved email, if someone saved it.The gaps are named on receipt #1; the evidence request cites that receipt's hash; receipt #2 shows exactly what came back and what didn't.
Was the standard applied consistently, or was this one waved through?An assertion about policy.The same sealed thresholds and the same weight_version appear on all 46 comparable decisions in the period. Deviation would be visible.
Was the record changed after the fact?You are asked to trust the document management system.Any edit breaks the chain from that point forward, and the RFC 3161 token independently fixes the date. Neither depends on Meridian's word.
Could an independent party reach the same conclusion from the same facts?No — the reasoning was never captured in a re-executable form.Yes. The reviewer re-runs the arithmetic on their own machine, running none of Meridian's software, and reproduces the identical hash. That is the whole design.
What diligence actually requires. Not that the decision turned out well — batches fail for reasons nobody could have known. What a reviewer is testing is whether a reasonable process was applied to the information available at the time, and whether that can be shown rather than asserted. A sealed, point-in-time-gated, independently reproducible receipt is a direct answer to that test. It is equally an answer when the decision was to hold or to fold — which is where conventional records are weakest, because caution normally leaves no trace at all.

08Day 180 — the backtest that changes the rules

3 January 2027. Meridian has 46 sealed decisions in this class. Every one can be re-run exactly as issued. Now the outcomes are known.

Feature examinedWhat the sealed receipts showSurvives false-discovery control?Change made
soh_algorithm_disclosure absent6 decisions where it was absent; 6 of 6 later produced a commissioning or warranty disputeYes — stronglyStays critical, and the required class is raised from any to verified
certificate_register_resolutionA feature nobody was weighting. 3 of 46 receipts carried a cited certificate that failed to resolve; 3 of 3 became disputesYesPromoted to a weighted feature; register resolution becomes a mandatory pre-check on any cited ID
renewable_energy_share_manufacturing absentCaused 11 of the period's 17 holds. Across all 46, its value shows no relationship to any downstream defect, dispute, or regulatory challengeNoWeight drops to zero — demoted out of the sufficiency-critical set. It remains a reporting obligation; it was never a sufficiency condition
material_origin_cobalt at modeled 0.7214 decisions proceeded at CAUTION on this basis; zero downstream failuresNo — not significant either wayNo change. Do not tighten a threshold on a hunch; 14 observations is not enough to justify it
Effect on the next periodhold rate: 17 of 46 (37%)  →  6 of 46 (13%) on the same evidence
downstream failures: no increase
avoided hold cost: 11 × $12,400 ≈ $136,400 per half-year
newly caught: 3 unresolvable citations that previously passed

Two properties make this legitimate rather than self-serving. First, every earlier receipt still reproduces exactly as issued — the new weights carry a new version number and apply only to decisions made after the change, so nobody can claim the past was reinterpreted to look better. Second, a feature is only promoted if it survives a false-discovery-rate control applied across every hypothesis ever tested — which is what stops a team from fishing through forty variables until something looks predictive. Both are covered by the patent's fourth independent claim.

The mechanism, in ordinary language, is on the Better Decisions through Backtests and Recursive Improvement page.

Reminder — exemplary All names, identifiers, certificate numbers, dates and figures above are constructed for illustration. The receipt structure, the gating arithmetic, the sealing and anchoring steps, and the backtest mechanism are real and are the same ones you can execute yourself in the 5-step demo and the public verifier.
Build this receipt yourself → The arithmetic, explained → Put a number on it →