How it works

Capture evidence once. Preserve its provenance. Evaluate it under many methods.

AgEvidence connects operational records from livestock technologies, sensors, laboratories, processors, models and supply-chain systems to a portable evidence contract — without replacing the systems that created them.

Evidence-to-reliance workflow

Five steps

Step 1

Submit one representative flow

one signed operational event;
one API payload;
one measurement output;
or one controlled source manifest.

Step 2

Map it into the evidence contract

source identity;
authority;
event time;
schema and software version;
entity relationships;
rights;
limitations;
parent evidence;
signatures or source commitments.

Step 3

Inspect the gaps

absent;
inconsistent;
unsupported;
outside a model domain;
awaiting human review;
restricted;
superseded.

Step 4

Apply a bounded profile

methodology;
buyer requirement;
assurance profile;
country adapter;
program contract;
institutional review context.

Step 5

Produce a portable artifact

what evidence is present;
what was reviewed;
which profile was applied;
what limitations remain;
what the artifact supports;
what it does not establish.

Evidence contract

What the contract binds

The evidence contract is a canonical representation of a record and everything required to inspect it later: who produced it, under what authority, about which entity, interpreted by which software and method version, and with what rights and limitations attached. Historical evidence is never rewritten when a profile changes.

evidence contract (abridged)

{
  "evidence_id": "ev_01HN7...",
  "source": { "system": "dosing-controller", "authority": "org:apex-livestock" },
  "subject": { "herd_id": "H-2291", "property": "PIC:QABC1234" },
  "occurred_at": "2026-03-14T22:10:04Z",
  "schema_version": "agev.event.v1",
  "software_version": "controller 4.2.1",
  "parents": ["ev_01HN6..."],
  "rights": { "owner": "org:apex-livestock", "reliance": "not-granted" },
  "limitations": ["calibration record not linked"],
  "commitment": { "alg": "ed25519", "sig": "3f9c..." }
}

Trust states

Four separate questions

Technical integrity

Is the record intact and traceable?

Scientific interpretation

What does the evidence support scientifically?

Method compatibility

Does it satisfy a specific profile?

External reliance

What did a buyer, verifier or institution decide?

A valid signature is not proof of scientific efficacy. Method compatibility is not registry approval. Artifact generation is not external acceptance. Payment is not evidence quality.

Lineage

Source to artifact

01Operational records
02Evidence contract
03Gap and review state
04Method / buyer profile
05Bounded reliance artifact

Map an Evidence Flow Review an example artifact