The whole corpus in one list. Arriving from a narrative orders it by relevance to that narrative; nothing is hidden from any of them.
States the thesis in one place: why agricultural evidence is becoming infrastructure, why the interoperability layer is the defensible position, and how reliance becomes revenue.
Sizes the demand created by disclosure regimes, lender requirements and supply-chain commitments, and shows why demand arrives as a verification problem rather than a software problem.
Traces the reporting obligations that convert voluntary agricultural claims into audited assertions, jurisdiction by jurisdiction.
Defines the problem the company exists to solve: agricultural claims are produced by incompatible methods and cannot be relied on across institutional boundaries.
Positions our approach against the existing measurement and provenance literature, and marks where the literature genuinely runs out.
Bridges science and system: turns the evidence problem into an architecture with stated invariants, boundaries and failure modes.
The single representation everything else agrees on. If this model is right, interoperability follows; if it is wrong, nothing above it holds.
Turns the evidence model from a document into something that can fail. Conformance is what makes third-party implementations possible.
The distribution mechanism. The SDK is free because adoption of the model, not the software, is what creates the reliance position.
Reference implementation of signing, provenance chaining, and deterministic verification invariants; independent third-party reconstruction remains unproven.
The queryable layer where evidence accumulates across boundaries and stays attributable to its source.
Defines the moment a third party relies on an assertion — the event the business model prices.
Converts adoption into reliance events into revenue, with the sensitivities stated openly.
Primary demand signal in buyers' own language, including the objections that recur.
A reference integration workflow exercised against the current implementation and fixtures; not an external production integration.
The single programme that tests the investment, technical, scientific and diligence claims simultaneously, with pre-registered success criteria.
Explains the wave structure: why portfolio companies are the fastest route to a corpus that outsiders can rely on.
Sequences the research so each paper has an architectural, product, commercial and go-to-market consequence rather than sitting apart from the company.
Maps each buyer and regulator requirement to the evidence-model field that satisfies it — the crossing point of market and schema.
Every load-bearing claim with its status, evidence, counter-evidence and the test that would move it.
Named risks with severity and mitigation, including the ones without satisfying mitigations.
How a private evidence model becomes a shared one without the owner capturing it — the credibility condition for standardisation.
Works through who else could occupy this position — incumbents, platforms, registries, consultancies — and what would have to be true for them to win.
When evidence from different methods is combined, uncertainty must compose honestly. This note states how, and where the approach breaks down.
Baseline instrumentation for SDK integrations, evidence volume and reliance events; external adoption and reliance are not yet established.
Every registered artifact remains visible from one index; source files are linked when filed. The current lens changes recommended reading and the explanation of why a document matters; it does not hide inconvenient evidence.
A first-time reader should see the purpose of the artifact before the file name: what question it answers, what it does not prove, what status it carries, and which part of the AgEvidence thesis depends on it.