Watch premises signals, assemble the movement, permit and indemnity evidence an event needs, and prompt the call — the accredited veterinarian diagnoses and reports, and the state official decides the movement.
A pen goes off feed, and the agent pulls the production, mortality and water records behind it.
02
A tank result comes back, and the agent traces it to the herds and hauler routes that fed the load.
Reason
03
A zone opens — screwworm has been live in Texas since June 2026 — and the agent maps the sites inside each ring.
04
A load is planned, and the agent reads the movement terms in force for both states since the April 2026 update.
05
A permit is needed, and the agent assembles the traceability, surveillance and biosecurity evidence for it.
Decide
06
An audit clock runs down, and the agent flags the lapse the 2024 indemnity rule turns into lost eligibility.
07
A flock is depopulated, and the agent builds the inventory, valuation and mortgage-consent packet.
Out
08
An event closes, and the signals, the packet, the permit and the veterinarian's call stay on the premises.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent watches and assembles; a veterinarian diagnoses and reports, and the state animal health official decides the movement.
Example workflow
One event, signal to permit
AgentHuman
1Signal receivedProduction drop, mortality spike, bulk-tank result or a detection posted nearby
2Context assembledPremises records, movement history, zone status and audit validity, each with its named source
3Event packet draftedSignals, affected premises, permit evidence and confidence
4Controls appliedZone-ring checks, state-pair movement terms, audit-validity checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is reported or moved at any of them — the agent is assembling, and the veterinarian's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the herd veterinarian to review.
Low confidence
Adds a biosecurity coordinator read first.
Veterinarian review
The packet is held with its signals, its zone status and the confidence.
Approve · Edit · Hold for a farm visit
Approved — released to report▼
6Herd and premises records updatedOnly where write access and approval policy allow it
7Outcome evaluatedTime to report, permit turnaround, audit lapses and corrections made after the movement
Edits
Every veterinarian edit is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Diagnosing the disease or confirming a case.
Making the report to the state animal health official.
Granting or issuing a movement permit.
Signing a certificate of veterinary inspection.
Automation boundaryAgent acts unaided
✓Watch production, mortality and bulk-tank signals.
✓Assemble the evidence a permit application needs.
✓Track zone rings, premises status and audit validity for the coordinator.
✓Prompt the call, and hold the packet for the herd veterinarian to work from.
Any write happens inside the boundaries agreed at implementation, never ahead of a permit.
Signing the appraisal and indemnity claim form.
Setting zone boundaries or premises designations.
Passing or waiving an APHIS biosecurity audit.
Changes to zone, movement or reporting rules.
Example output
One event packet, annotated
Everything the agent assembles is attached to the record it was drawn from.
Event-packet output · single premisesIllustrative example
Premises
Signal raised
Zone status
Source of record
Confidence
Attribution
Layer house, contract grower
Daily mortality has climbed for two days and water intake is down in one house
Buffer zone
Barn controller and daily log
91%
Named veterinarian and accreditation ID
As receivedTaken from the barn controller and the daily log — nothing on this side is written by the agent.
Signals usedDaily mortality logWater and feed intakeNearby detection notice
Why this was raisedBirds that die before depopulation are not indemnified.
ActionApproveEditHold for a farm visit
What the score decidesBelow the configured threshold the packet picks up a coordinator read first.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every premisesFrom the premises records
03Assembly
Assemble from the record
Draw on the premises records and the zone, movement and audit rules configured for the operation.
01Approved path
Reporting beats diagnosing
Routine surveillance and permit evidence arrive already gathered.
02Human review
Send the veterinarian to the risk
Threshold crossings and lapsing audits are marked, so the veterinarian's read starts where the risk sits.
04Build an evidence trail
The event, the premises it was raised on and the veterinarian who called it stay on the record.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Herd & flock recordsDairyComp 305 · PCDART Poultry flock systems
A whole-system reporting time can look acceptable while a few premises cohorts absorb most of the rework that delays it. Nestack reports the packet-rework rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Contract-grower premises
8.9%
3.8×
Review
Interstate dairy movements
5.2%
2.2×
Review
Buffer-zone premises
3.7%
1.6×
Watch
Single-site owned premises
2.1%
0.9×
Normal
Bar: packet-rework-rate lift vs. the single-site baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
Every cycle closes with a new case
A cycle closes when the late report is a case the next release has to catch. That suite is what the next event worked is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Packet-rework rate rises in a premises slice.
02Diagnose
The four days between the first sick pen and the call are walked back until the cause narrows to one.
03Improve
The correction is numbered and the events that produced it are pinned to the note.
04Verify
One movement case still failing is enough to keep the release on the bench.
05Learn
The case is kept, and the zone rules are updated in the same change.
Learn → DetectThe return edge. The next event is worked against a suite one case longer.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, event workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Disease-event workflow and premises boundary definition.
02Herd, flock and lab source assessment.
03Zone-ring, movement-term and audit-validity mapping.
04Premises-record ingestion and mapping.
05Signal logic and record binding.
06Confidence scoring and event routing.
07Veterinarian review workflow.
08Herd-record and permit-portal integration.
09Movement and reporting cases.
10Guardrails and permit controls.
11Premises-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne premises, one speciesProductionProduction herd systemsAdvancedMultiple sites / states
Introduced at Pilot
Signal watching to your thresholds✓✓✓
Veterinarian review✓✓✓
Reporting-speed baseline✓✓✓
Introduced at Production
Reporting by premises—✓✓
Review workflow in your systems—✓✓
Approved write-back—✓✓
Herd-record integration—✓✓
Introduced at Advanced
Multi-state movement rules——✓
Multi-stage event approvals——✓
High premises count——✓
Multi-site movement controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, premises count, review controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your premises list and species mix→Premises-record ingestion and mappingWeek 1
02Representative past events and movements→Signal baseline, threshold extraction and record bindingWeek 2
03Your zone, movement and audit rule sources→Zone, movement and audit rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Herd, flock and lab assessment, then integration setupWeek 2
05Movements you would not want permitted→Outbreak cases and the evaluation suiteWeek 4
06What no movement may proceed without→Confidence scoring, event routing, guardrails and permit controlsWeek 3
07Named veterinarians to review packets→Veterinarian review workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Each band lands where the work lands, which puts evaluation and the first live events in one week.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Event workflow discovery, rule mapping and the automation boundaryW2Herd, flock and lab integration and the signal baselineW3Event workflow, confidence logic and veterinarian-review controlsW4Evaluation suite, movement-rule checks and failure-mode testingW5Permit-portal integration, pilot events and targeted correctionsW6One surveillance cycle run under the herd veterinarian, then handover
Reading the bandA bar covers the weeks its work is named in, and nothing else. The week 5 overlap is real, not padding.
At the end of W6Validation closes on live events, and Agent Care takes over monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Agriculture AI agent
Build a biosecurity agent around your premises and your veterinarian.
Show us your premises list, your movement terms and who you call. What changes first? Time-to-report — and on a poultry claim that is the number deciding what is recoverable.
