Evidence you retrieve, not reconstruct
What "audit-ready" should actually mean when agents make the deal — and what a DIFC-ready evidence pack contains.
Ask a team for the history of a disputed agreement and watch the reconstruction begin: email threads, chat exports, a CRM timeline, two contradictory PDFs named final. Each artefact is real; none is the record. The gaps get filled with memory, under deadline, by the people with the most at stake.
Agent commerce makes this worse — more transactions, faster, with drafts generated rather than typed. It also makes the fix cheaper: when negotiation runs through one protocol, the record writes itself.
Reconstruction is what you do when the record wasn’t built to be retrieved.
What the pack contains
A Subchain evidence pack is the ordered event log of one negotiation: every proposal and counter with its sequence number, every policy flag, the halt at the gate, the named approval with timestamp and identity, the binding acceptance. It exports as an ordered PDF for humans and JSON with a checksum for systems.
Append-only matters legally: corrections are new events, so the history you produce is verifiably the history that happened. The export itself is logged — retrieval leaves a record too.
Jurisdiction, named
Subchain is domiciled in DIFC, and the pack is designed with DIFC dispute resolution in mind — alongside internal audit and regulatory enquiry. Your agreements keep whatever governing law your templates specify; the record serves the forum you end up in.
More field notes
Sizing a market honestly at Pre-Seed
Our market slide has three numbers and three disclaimers. Here’s the method, and why we’d rather under-claim than defend a fantasy.
The Subchain team
5 min read
The connector math: one integration versus N
Bespoke counterparty integrations scale quadratically in the market and linearly on your backlog. Both curves are bad. Here’s the arithmetic.
The Subchain team
4 min read
Approval gates people don’t route around
Governance fails socially before it fails technically. Notes on designing thresholds that survive contact with a busy quarter.
The Subchain team
6 min read