Persistent Farm Memory · Preview

FieldState
The Farm Memory That Outlasts Every Conversation

Every diagnosis, decision, and treatment logged through FieldGuide is captured as structured farm history in FieldState. It turns ephemeral AI conversations into a living, queryable record of your farm — season after season.

FieldState main screen showing farm memory, records, and historical context

The Problem It Solves

Every AI Conversation Ends. Every Insight Disappears.

Most AI tools — including field assistants — operate statelessly. You describe your crop, get advice, close the session, and start from zero the next time. The AI has no memory of what was diagnosed last month, what was sprayed, what worked, or what failed. Each session is an island.

For farmers managing crops across multiple seasons, this is a structural problem. Agronomic decisions are cumulative. A disease that recurs in the same plot two seasons in a row is a systemic signal — but only if someone remembers the first time it happened.

FieldState fixes this. It captures the output of every FieldGuide session as structured farm data — building up a persistent picture of the farm that any authorised user can query, review, and act on.

Without FieldState
  • Repeat your farm context every session
  • Treatments you applied — unrecorded
  • Diseases diagnosed two seasons ago — forgotten
  • Agronomist handover starts from scratch
  • No way to ask "what happened last month?"
With FieldState
  • Farm context is carried forward automatically
  • Every treatment logged with date and rationale
  • Disease history queryable across seasons
  • Agronomists and extension officers share the same history
  • Ask "what did I spray last month?" — get a real answer
FieldState turns conversations into records. Records into patterns. Patterns into better decisions.

What FieldState Captures

Four Core Capabilities

FieldState is not a simple log. It structures farm knowledge so it can be queried, shared, and reasoned over — closing the loop between real-time guidance and accumulated farm intelligence.

01

Crop Lifecycle History

Tracks what was planted, when it was planted, what growth stage it reached, what problems emerged, and how they were resolved — for every crop season. Instead of a farmer's memory, FieldState builds a structured timeline the farm can reference for years.

Planting records Stage milestones Season history
FieldState crop season screen with planting and growth history
02

Treatment & Decision Audit Trail

Every recommendation acted on through FieldGuide — which fungicide was applied, what dose, on what date, against what diagnosed condition — is stored with context and rationale. This creates a tamper-resistant audit trail that supports accountability and future decision-making.

Treatment logs Decision rationale Date-stamped
FieldState action screen highlighting items that need follow-up and treatment history
03

Queryable Farm Memory

Ask natural-language questions against your farm's history: "What diseases appeared in Plot B last season?" or "What did we spray in March?" FieldState structures the data so FieldGuide can answer these questions with real, recorded information — not hallucinations.

Natural language query Structured recall No hallucination
FieldState searchable farm memory interface with prior decisions and records
04

Pattern Detection Across Seasons

A disease appearing in the same location for the third consecutive wet season is not bad luck — it is a systemic signal. FieldState surfaces recurring patterns across stored events so farmers and agronomists can address root causes, not just individual outbreaks.

Recurrence detection Seasonal patterns Systemic signals
FieldState timeline view surfacing repeated crop issues across seasons

How They Work Together

FieldGuide Goes With You.
FieldState Remembers.

FieldGuide is the tool you reach for when standing in the field — diagnosing a disease, checking growth stage guidance, deciding what to spray. It is real-time, conversational, and context-aware.

FieldState is what makes FieldGuide accumulate. Every interaction that produces a meaningful outcome — a diagnosis confirmed, a treatment applied, a decision logged — is written into FieldState as structured farm data. The next time you open FieldGuide, it already knows your farm's recent history.

Together, they close the loop between real-time field guidance and accumulated farm knowledge. Shared visibility means farm owners, agronomists, and extension officers all access the same history — no separate silos, no repeated explanations.

FieldState add farm screen showing how farm context is structured at setup
Step 01 — In the Field

Farmer uses FieldGuide to diagnose a crop issue, ask about growth stage, or get treatment guidance.

Step 02 — Captured

FieldState records the diagnosis, recommendation, and any actions taken — structured, date-stamped, and linked to the crop.

Step 03 — Queryable

Farm owner, agronomist, or extension officer reviews the history — asking questions, spotting patterns, sharing context.

Step 04 — Better Decisions

The next FieldGuide session starts with full context — no repeating history, no missing information, no guesswork.

Try the Playground

Your Farm Has a Memory Now. Use It.

FieldState is available as a preview via the Playground. Explore how structured farm memory works alongside FieldGuide — and see what persistent agricultural intelligence looks like in practice.