SRCSource evidence
Observation, boundary, zone, plan, or measurement that begins the chain.
Interoperability review workspace
Trace the record.
Protect the meaning.
Build a visible path from source evidence through farm software, exchange, machinery, field work, returned records, and review—then expose every owner, format, transformation, and unresolved claim.
01Intent
02Lane
03Systems
04Evidence
05Gate
06Export
Choose the journey before the format.
Start from the job: send reviewed intent to a machine, return work evidence, or turn a sensor record into a reviewed decision.
Make every handoff visible.
The lane shows the selected workflow in order. A present stage is still incomplete until its exact system, format, and owner are declared.
- 01SRCSource evidenceFORMAT OPEN
- 02FMISFarm softwareFORMAT OPEN
- 03XFERExchange layerFORMAT OPEN
- 04MACHMachine systemFORMAT OPEN
- 05WORKField operationFORMAT OPEN
- 06BACKReturned recordFORMAT OPEN
- 07QAReview & analysisFORMAT OPEN
Name the system, format, owner, and change.
Record what participates and what happens to the record. Transformation notes expose aggregation, conversion, filtering, enrichment, and lost context.
FMISFarm software
Organizes field identity, context, decisions, and planned work.
XFERExchange layer
File, API, cloud connection, removable media, or message route.
MACHMachine system
Display, controller, or implement that receives or records data.
WORKField operation
The physical work and conditions that give records their meaning.
BACKReturned record
As-applied, coverage, machine, observation, or result data.
QAReview & analysis
Reconciles intent, actual work, exceptions, and future decisions.
Test meaning, not only transport.
A successful upload can still attach data to the wrong field, change units, lose lineage, confuse targets with results, or retain data beyond the owner's intent.
Can every system refer to the same field, operation, product, machine, and time?
Who can send, receive, transform, retain, and revoke access?
Are the exact object types, versions, companion files, and limits known?
Are quantity, unit, denominator, timing, and missing-value rules preserved?
Can the record be traced through every edit, conversion, aggregation, and export?
Can intended work be distinguished from what the machine actually recorded?
Are source copies, versions, deletion, failure, retry, and exit behavior explicit?
See exactly why the chain is blocked.
The gate stays blocked while a required stage, profile, or evidence topic is open. Declared evidence still requires review before it becomes verified.
FLOW STATEblocked
System, format, or owner missing at Source evidence.
- required stages
- 7
- profiles open
- 7
- unknown evidence
- 7
- transformations named
- 0
System, format, or owner missing at Source evidence.
Evidence unknown: Field and object identity.
06 / BROWSER-LOCAL HANDOFFExport the architecture, never the farm data.
The JSON contains only this review model. It carries no field geometry, machine records, credentials, API tokens, prescriptions, or personal data.
Keep interoperability accountable.
Continue into field-data interoperability, farm data governance, and the ISO 11783 farm-software view.