AMIGA Operations Toolkit

Field robotics needs an operations layer.

Agricultural robotics field deployments produce a steady flow of operational information that has nowhere structured to live. Machine state changes between visits. Site geometry — bed layouts, irrigation lines, headlands, access constraints — exists in operator memory or scattered notes. Pass planning happens on whiteboards or not at all. Visit-to-visit continuity depends on whoever was there last remembering what they did.

The result, across small-fleet field deployments, is that a real fraction of each visit gets spent reconstructing context that should already be known. Operational discipline that's standard in enterprise infrastructure — documentation, change control, sustained accountability — has no comparable layer in field robotics.

A practical field loop.

The toolkit supports a structured field workflow. Each tool addresses one stage of the work an operator does onsite.

1. Prepare the visit — sites, machines, prior context.
2. Inspect machine state and verify readiness.
3. Collect machine readout and access diagnostics.
4. Capture site and bed geometry.
5. Plan and review operational passes.
6. Document visit outcomes — observations, issues, follow-up.
7. Share a clear report with the farm or trial team.

Next-Visit Access Pack.

A USB-based field package for collecting machine state and diagnosing access conditions when remote access is uncertain. Includes a read-only machine readout script, a read-only access-model diagnostic, an optional public-key install helper with explicit-authorization safeguards, and an onsite operating guide.

Framed as an authorized field-readout workflow with trial-coordinator authority respected — not a bypass tool. The only modificatory component (the optional public-key install) requires explicit authorization from the responsible on-site or trial authority before any system modification.

Part of the AMIGA project scope, supporting the same field workflow as the four tools.

Before: field robotics deployments without a structured software layer for readiness, planning, and operational record-keeping. After: a four-tool field toolkit covering machine state, field geometry, pass organization, and visit continuity.

Offline-first, operator-controlled.

The toolkit is offline-first by design — the suite functions completely without server connectivity after the initial page load, enabling field-deployed use. No backend service, no account requirement, no network dependency at the edge. State is stored locally and encrypted; cross-tool context propagation is handled in shared workspace files that an operator can save, transfer, and version.

Generation-aware support covers both V2.x (farm-ng) and V3.0 (Bonsai) Amiga platforms, with normalization handled in the data layer so that operators working across both generations see consistent tool behavior.