Agriculture & Food

Farm Agronomy Copilot

Designed for Farmer or agronomist

Help the agronomist turn per-field agronomic history, soil tests, in-season imagery and weather into a defensible field-level recommendation for nutrition, irrigation or crop protection, with label restrictions and re-entry intervals enforced before any prescription is written.

Contract AGR-01 · primary aggregate FieldSeasonRecord · mode loading

Decision brief

Agronomist approval and machine release: evidence ready for review

This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.

Decision signals

The evidence and control points that shape this recommendation.

Decision owner

Certified agronomist or grower

The named role remains accountable for the consequential decision.

Governed evidence

6 record types

Structured records and cited text ground the recommendation.

Workflow

5 controlled stages

Each transition records its input, output, status, and audit context.

Human controls

1 approval gate

Approval gates prevent the copilot from making consequential decisions.

Business problem

Sentinel imagery on a 148-acre irrigated corn field at V10 shows a 22-acre NDVI depression on the sandy east zone.

Decision to make

Help the agronomist turn per-field agronomic history, soil tests, in-season imagery and weather into a defensible field-level recommendation for nutrition, irrigation or crop protection, with label restrictions and re-entry intervals enforced before any prescription is written.

Outcome to show

ApplicationRecord gives Certified agronomist or grower the evidence needed to begin the final governed business outcome, with the decision trail retained for review.

  1. 1Field condition sensing
  2. 2Agronomic diagnosis
  3. 3Label and threshold grounding
  4. 4Prescription drafting with restriction checks
  5. 5Agronomist approval and machine release

Step 1 of 5

Ready: Start with the business question, then use the single button above.

The output appears here immediately. More technical evidence remains available below.

System logic, GenAI, and human accountability

The demonstration keeps deterministic controls, AI assistance, and approval separate.

System logic

Source systems enforce identity, workflow order, policy filters, and record updates.

GenAI contribution

Retrieval and generation assemble relevant evidence into a cited recommendation or draft.

Human accountability

Certified agronomist or grower verifies material claims and approves the consequential action.

Workflow stages

Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.

Seeded record
Loading
Document type
Loading
Container
Loading
Partition key
Loading
Current stage
Loading

API demonstration guidance

Run a stage to see its explanation, evidence, full request, and full response.

Grounded chat

Ask a question and receive an answer grounded in retrieved FieldSeasonRecord evidence.

Answer and evidence

Select a starter question or enter your own.

Evidence

Domain implementation workspace

Loaded live from /api/config, /api/domain/model, and /api/domain/sample.

Domain objective
Help the agronomist turn per-field agronomic history, soil tests, in-season imagery and weather into a defensible field-level recommendation for nutrition, irrigation or crop protection, with label restrictions and re-entry intervals enforced before any prescription is written.
Primary aggregate
FieldSeasonRecord
Primary container
fieldSeasonRecords
Hierarchical key
/tenantId + /fieldId
Schema version
1

Sample scenario

Sentinel imagery on a 148-acre irrigated corn field at V10 shows a 22-acre NDVI depression on the sandy east zone. The copilot correlates it with the spring soil test showing 9 ppm potassium in that zone, two scouting notes of firing on lower leaves, and 4.1 inches of rain in the prior ten days. It cites the state extension sufficiency range and the fertilizer label, drafts a zone-specific 60 lb per acre potash application with a three-day window before the next forecast rain, and flags that the neighboring zone needs no application. The agronomist approves; the zone-rate file is released to the spreader and the as-applied record returns 21.6 acres covered.

Physical Cosmos DB containers

Every container provisioned for this accelerator with its hierarchical partition key.
Container Role Hierarchical partition key Document types
fieldSeasonRecords Primary /tenantId + /fieldId Field, SoilTestResult, ScoutingObservation, PrescriptionDraft, ApplicationRecord
agronomicLabelLibrary Reference /tenantId + /cropCode AgronomicGuidanceChunk

Document types

Contract document types, their owning container, and their identifier pattern.
Type Container Partition key Identifier pattern Embedding fields
Field fieldSeasonRecords /tenantId + /fieldId field::{fieldId} None
SoilTestResult fieldSeasonRecords /tenantId + /fieldId field::{fieldId}::soil::{sampleDateUtc}::{zoneCode} None
ScoutingObservation fieldSeasonRecords /tenantId + /fieldId field::{fieldId}::scout::{observedAtUtc}::{observationId} None
AgronomicGuidanceChunk agronomicLabelLibrary /tenantId + /cropCode crop::{cropCode}::guidance::{guidanceDocId}::{chunkOrdinal} chunkVector
PrescriptionDraft fieldSeasonRecords /tenantId + /fieldId field::{fieldId}::prescription::{prescriptionId} rationaleVector
ApplicationRecord fieldSeasonRecords /tenantId + /fieldId field::{fieldId}::applied::{appliedAtUtc}::{prescriptionId} None

Query patterns