Keep current the evidence a producer is asked for again and again — chain of custody per shipment, certificate and audit clocks, answers still tied to a source. The certification sits downstream.
A parcel is despatched, and the despatch, weighbridge and seal records are pulled from supported sources.
02
A lot is blended from two pits, and each contributing lease is carried rather than the template default.
Reason
03
A questionnaire arrives, and each prior answer is re-checked against the source document that supported it.
04
An audit falls due, and the scheme cycle the operation is actually enrolled in is read, not a generic calendar.
05
A certificate nears expiry, and the shipments and answers leaning on it are listed while there is still time.
Decide
06
An origin claim rests on an assay, and the certificate is drawn from the assay copilot rather than restated.
07
A tracing request lands, and the extraction and transport records for that consignment are assembled to a date.
Out
08
A pack is retained as a dated version, beside the records under it and what the answering manager was shown.
09
A write action runs only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles and keeps the evidence current; a named manager answers the customer, and the operator carries every declaration it signs.
Example workflow
One shipment, pit to pack
AgentHuman
1Records receivedDespatch, weighbridge, seal, assay and lease records
2Custody assembledTransfers, blend inputs, certificates and prior answers, each with its named source
3Evidence pack draftedCustody chain, supporting documents, open gaps and confidence
4Controls appliedCustody-continuity tests, certificate-currency checks, scheme-scope tests and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is answered at any of them — the agent is assembling evidence, and the manager lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the commercial manager.
Low confidence
Adds a technical read first.
Manager review
The pack is held with its records, its open gaps and the confidence.
Approve · Amend · Send to technical review
Approved — released to answer▼
6Evidence register updatedOnly where write access and approval policy allow it
7Outcome evaluatedAmendment distance, open-gap outcomes, audit findings and post-answer corrections
Amendments
Every manager amendment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Certifying the origin of a parcel — a named person does that.
Signing a conformity or due-diligence declaration.
Answering a customer, a scheme or an auditor.
Deciding whether a scheme criterion is met.
Automation boundaryAgent acts unaided
✓Assemble the chain-of-custody record for a despatched parcel.
✓Carry each claim with its source, and flag what has none.
✓Track certificate expiry and the audit cycles entered.
✓Draft the questionnaire response and hold it for the manager.
Writes run only inside the boundaries agreed at implementation, and never ahead of the manager.
Committing the site to a scheme or its assurance clock.
Warranting origin in a sales or offtake contract.
Withdrawing or correcting a declaration already issued.
Changes to scheme, evidence or approval rules.
Example output
One shipment record, annotated
Everything the agent assembles is attached to the record it was drawn from.
Evidence pack output · single shipmentIllustrative example
Counterparty
Custody line
Parcel reference
Source of record
Confidence
Basis of record
Concentrate offtake
Blended in a stockpile from two pits under separate leases
MC-0412-B
Stockpile transfer note
84%
Weighbridge and seal records
As receivedTaken from the despatch record and the transfer note — nothing on this side is written by the agent.
Source facts usedWeighbridge ticketStockpile transfer noteContainer seal record
Why this is openThe parcel carries material from two leases, and the template names only one.
ActionApproveAmendSend to technical review
What the score decidesBelow the configured threshold the pack picks up a technical read before the manager sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every shipmentFrom the despatch and assay records
03Assembly
Build the custody record
Records already on file are joined into a chain; what is claimed to a customer stays with the manager who answers.
01Approved path
The signer is downstream
Regulation (EU) 2017/821 binds the Union importer, not the mine. What is at stake upstream is market access.
02Human review
One half is not a second product
If you run the shipped commercial and ESG agent, the questionnaire half is a feature of it. What is distinct here is the per-shipment record.
04Build an evidence trail
The shipment, the origin evidence under it and the manager who answered stay on the pack.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Despatch and shippingWeighbridge · seals Bills of lading · draft survey
Assay and laboratoryLIMS · assay certificates Sampling records
Commercial systemsSAP · Oracle ERP Offtake and sales records
Agent
Supply-chain evidence
Reads the records Assembles the pack Holds for the manager
A shipment-level evidence-coverage figure can read as complete while a few counterparty and shipment types carry most of the amendments. Nestack reports by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Blended stockpile parcels
6.4%
3.7×
Review
Refiner and smelter audits
4.9%
2.8×
Review
Forced-labour tracing requests
3.4%
1.9×
Watch
Routine offtake despatches
1.2%
0.7×
Normal
Bar: amendment-rate lift vs. routine-despatch baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
The loop closes on a new test
A cycle closes when the unanswerable question is a regression case. That suite is what the next pack assembled is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendment rate rises for one counterparty slice.
02Diagnose
The eleventh customer asking the same question a different way is read back through the packs until the cause narrows to one.
03Improve
The fix carries a number, and the shipments that forced it travel with it.
04Verify
Nothing goes out until every touched shipment case has passed again.
05Learn
It is kept permanently, and the evidence rules are amended alongside it.
Learn → DetectThe return edge. Detection next time starts from a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, evidence workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Evidence workflow discovery and boundary mapping.
02Despatch and assay source assessment.
03Scheme, certificate and audit-cycle rule mapping.
04Record ingestion and custody joining.
05Pack assembly and source binding.
06Confidence scoring and gap routing.
07Manager review workflow.
08Despatch and assay-system integration.
09Custody and questionnaire cases.
10Guardrails and disclosure controls.
11Shipment-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne commodity, one routeProductionProduction source systemsAdvancedMultiple sites / schemes
Introduced at Pilot
Evidence assembly per shipment✓✓✓
Manager answer approval✓✓✓
Custody-continuity baseline✓✓✓
Introduced at Production
Reporting by counterparty—✓✓
Exception workflow in your systems—✓✓
Approved write-back—✓✓
Despatch-and-assay integration—✓✓
Introduced at Advanced
Multi-scheme mapping rules——✓
Multi-stage commercial approvals——✓
High shipment volume——✓
Multi-scheme evidence controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your shipment types and counterparties→Scheme, certificate and evidence rule mappingWeek 1
02Representative prior questionnaire responses→Record ingestion, custody joining and the assembly baselineWeek 2
03Your origin-claim policy and evidence standards→Evidence-pack mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Despatch and assay-system assessment, then integration setupWeek 2
05Packs you would not want re-checked→Certificate cases and failure-mode testingWeek 4
06What no origin claim may assume→Confidence scoring, gap routing, guardrails and answer controlsWeek 3
07Named managers to review the evidence pack→Manager review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phase widths follow the calendar the work needs, so the doubling seen at week five is not padding at all.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Evidence workflow discovery, scheme mapping and the automation boundaryW2Source integration and the custody-assembly baselineW3Assembly workflow, confidence logic and answer controlsW4Evaluation suite, certificate checks and failure-mode testingW5Assay-system integration, a pilot shipment and targeted correctionsW6One shipment cycle run under the commercial manager, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named in. The week 5 overlap is real, not padding.
At the end of W6When the shipment pack validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Mining AI agent
Build the evidence pack before the next questionnaire arrives.
Show us your despatch records, the schemes you are enrolled in and who answers. The certification is carried downstream — by the smelter, the refiner, the listed manufacturer, the importer of record — never by the mine. When an answer that already went out proves unsupported, the manager withdraws it, and the pack shows what they were shown when they gave it.
