Counter → field → reviewer

Turn a vague request into reviewer-owned evidence work.

MittiGuard Relay captures the field story, blocks unsupported sales, and sends an exact evidence task—not a chemical recommendation.

1

CaptureVoice, photo, field

2

ReconcileEvidence, not advice

3

BlockPolicy owns state

4

RelayTasks + human owner

NEW CASE READY

Invoice awaiting evidence

01

Farmer & field

Every handoff begins with a field-linked record.

Farmer name Field ID Crop Crop stage Farmer language

02

Counter story

Capture the request before anyone discusses an input.

Input type Requested product Farmer-reported symptom Voice-note transcript

Voice intakeBrowser transcription is optional and not stored as audio.

AI evidence intakeTurn the reviewed narrative and optional image into an editable evidence draft. It cannot authorize a sale.

03

Evidence package

Ambiguity belongs in a task, never in an invoice.

Soil Health Card / test dateLast input & date

⌁Demo field evidence (simulated)For live cases, attach a whole-plant or close-up image Prior input did not resolve the issue

Demo mode uses simulated evidence. The policy never recommends a pesticide, fertiliser, dose, or application timing.

Human-owned operations

Evidence Relay

A visible chain of custody from a blocked counter sale to qualified review.

LIVE LOCAL LEDGER

BLOCKED INVOICES0Policy-controlled

OPEN EVIDENCE TASKS0Assigned, time-boxed

REVIEW OWNERS0Human next step

01

Counter blockCase opened, invoice held

0

02

Field captureExact evidence requested

0

03

Extension reviewHuman owns next step

0

SELECTED HANDOFF

Choose a case

The Evidence Relay board loads your local cases.

WAITING

HANDOFF CODE——

No handoff selected.

OUTCOME LOOP

Record the observed field outcome.

Only extension review can write the observation that future Evidence Debt checks use.

CASE TRACEImmutable local audit

Select a case to inspect each policy and handoff event.

Copying the request prepares a field handoff message; MittiGuard does not send messages or release a sale automatically.

Farmer record

Field memory prevents repeat mistakes.

The ledger remembers outcomes—not just purchases.

GNT-14 · NORTH PLOTField history

—

Loading field history

The first relay case creates an auditable ledger event.

MEMORY RULE

Previous failure changes the next sale.

When an input did not resolve the recorded issue, the next similar sale goes to review instead of becoming a second guess.

Transparent evaluation

Safety bench

The claim is not disease-diagnosis accuracy. It is that ambiguity never becomes automated input authorization.

POLICY FIXTURES9 / 9

All paths end in hold or qualified review.

Evidence Debt benchmark

24 synthetic adversarial cases: exact field/crop boundary, 12 repeat matches, and 12 hard negatives.

100% ON THIS SCOPED FIXTURE

Blocked sale

Stale soil data, missing photos, failed inputs, and unlinked fields stop an invoice.

NO APPROVED-SALE STATE

Automatic Evidence Debt

An unresolved, similar field outcome is matched server-side—even if the dealer clears the failed-input toggle.

DEALER CANNOT BYPASS IT

POS Gate contract

Counter software receives a receipt with a decision digest, hold state, relay case, and handoff code.

SALE NOT RELEASED

Evidence handoff

Completing a task moves a relay stage only; it never releases the sale.

STATE REMAINS ON HOLD

Run npm test for policy fixtures, the scoped Evidence Debt benchmark, POS Gate contract, relay persistence, and model-output guard tests. Add locally validated expert cases before any real deployment.