Operator ingest

Updated: 2026-09-15 · R3

R3 applies the accuracy-review ingest rule in the body: a phone or iPad in a truck reports crew/device position, not the aircraft flight path or applied coverage. Provenance must be labelled. A telemetry or file export is not automatically a legally accepted pesticide application record.

Date: 16–17 August 2026

Owner: AT / Velocity EU

Audience: founders. Designed solution — how an existing crew’s plot, path, live monitoring, and as-applied evidence attach to one job object.

Companions: option-c-hybrid-fleet.md · canopy-fly.md · canopy-live.md · canopy-receipt.md · canopy-cue.md · docs/Canopy_Startup_Plan.md · docs/glossary.md

Facts are sourced as of 16–17 August 2026. No invented take. No invented seed size. No invented valuation. No unpublished prices. If a public Application Programming Interface (API) is not found, the row says NOT FOUND and the fallback (file / beacon / ASK). One adapter per vendor. Never a universal drone API.

Canopy does not assume remote-control authority over the aircraft. Canopy does not become an Original Equipment Manufacturer (OEM). We do not productise weapons or offensive Intelligence, Surveillance and Reconnaissance (ISR). We do not buy FRAME (EnduroSat satellite bus) Max. Published FRAME Max unit prices are order-size dependent (USD9.5m / 8.1m / 6.7m / 4.2m) [S49].

The problem

Marketplace crews already operate their own aircraft. Canopy must attach their plot, a provenance-labelled path, live watch, and as-applied artefact onto one job object. The live path and the legal path are different objects until an OEM as-applied log is imported and accepted.

Option C is the lock: operators bring DJI Agras / XAG now. A later canopy_fleet dock turns on only when a real week has no crew. That is steel we dispatch, not a factory we run. Full argument: option-c-hybrid-fleet.md.

If we pretend there is one drone API, we will either (a) take the remote and become an OEM, or (b) ship a live map that treats a truck phone as an aircraft. Neither is the company.

The solution — three layers

1. Job contract (ours, OEM-agnostic)

One job object. Not one per vendor.

Path source tags (exactly these):

Receipt prefers the OEM as-applied log when the crew can produce one. Beacon is good enough to watch the crew. It is not the aircraft path, not applied coverage, and not the legal artefact by itself. An imported log still requires field validation and acceptance before it can be treated as a candidate BFSA pack.

2. Operator console — v1 this year (Bulgaria handshake)

Canopy pushes the job to the iPad. The crew flies in the native OEM app they already trust — DJI Agras app on the remote, XAG One, or AgroSol Ground Control Station (GCS). Human remains Pilot in Command (PIC).

During the pass, the iPad (or a phone in the truck) is the live crew/device beacon the asset owner watches. Good enough for “watch the crew.” Not remote-control authority. Not the aircraft flight path or applied coverage. Label live_source = operator_beacon.

After landing, the operator imports the OEM export and confirms hectares, dose, start/end times. That write is a candidate evidence record. Nobody re-types a Bulgarian Food Safety Agency log. The export is not automatically a legally accepted pesticide application record.

Version 1 (v1) does not: remotely pilot the aircraft from Canopy; replace the Original Equipment Manufacturer (OEM) Ground Control Station (GCS); build a DJI FlightHub integration before a Dock or Matrice survey job exists; or raise capital to purchase aircraft.

3. OEM adapters — only when a public API actually exists

One adapter per vendor. Ship the file/beacon path first. Add a REST/MQTT adapter only after a public (or partner) API is in hand. Label partnership asks ASK, not facts.

Sourced OEM / system facts (as of 16–17 August 2026)

DJI Agras — spray. What Bulgarian (BG) crews actually fly

Do not claim a universal DJI agriculture API. Do not route Agras through FlightHub.

DJI Dock / Matrice — survey, later canopy_fleet. Not the spray path

XAG

Hylio

Pyka Pelican 2

Guardian Agriculture SC1 — do not plan an adapter

Company wound down late August 2025 (The Robot Report). Closed. Remove from any “we integrate them” list. No adapter.

Earth-observation / weather (cue, not fly)

These cue the plot and hold the window. They do not fly the aircraft.

Other named suppliers (link only — we do not integrate their drones)

UNL page confirmed 17 Aug 2026 (Center for Agricultural Profitability; 2026 Nebraska Agricultural Custom Rates). Plan INFOCA official Junta page is the Dispositivo INFOCA hub (Catálogo de medios 2026). A dedicated RPAS-tender landing page on junta.es was NOT FOUND; do not invent one. Civil/military retool stays Search and Rescue (SAR) / comms / software re-accreditation — no weapons.

v1 punch list

Schema now (job + operator profile):

• aircraft_oem
• aircraft_model
• gcs_app
• path_source
• path_geojson
• as_applied_uri
• live_source

First two BG handshake crews: record OEM + model on the operator profile. Ship the operator console plus KML / GeoJSON import. Live = beacon.

Do not build a DJI FlightHub integration until we have a Dock or a Matrice survey job.

Do not raise capital to purchase aircraft.

Do not assume remote-control authority.

Sources (accessed 16–17 August 2026)

• DJI Agriculture / SmartFarm: ag.dji.com, SmartFarm web
• DJI SDK agricultural-drone support: Mobile-SDK-Android #1350
• AirData Agras log path: app.airdata.com/wiki/Help/DJI+AGRAS
• FlightHub 2 OpenAPI: fh.dji.com user-manual OpenAPI; demo FlightHub-2-OpenAPI-V2-Demo
• FlightHub Sync 2.0 (MQTT / RTSP / Event API): DJI Enterprise Insights, 2 Apr 2026
• XAG: xa.com/en/p150, xa.com/en/pseries, open.xa.com
• Hylio: hyl.io; PIX4Dfields → AgroSol GeoJSON: PIX4D support
• Pyka: flypyka.com/pelican-2, flypyka.com/technology
• Guardian Agriculture shutdown: The Robot Report
• CDSE / Planet / EnduroSat / OpenWeather: URLs in the cue table above
• UNL 2026 custom rates: cap.unl.edu/customrates
• Plan INFOCA: Junta de Andalucía — Dispositivo INFOCA