Feedstock Carbon-Intensity & 45Z Documentation AI Agent

What this agent does

Documents the field, not the tax position

A pass is logged, and the agent pulls the field, the product and the rate behind it from the farm record.

A nutrient budget is filed, and it is read against subpart G of USDA's final rule of 29 June 2026.

Reason

A soil test is loaded, and its date is checked against the two-year window the report must be current for.

A tillage pass appears in year three, and the commitment behind an already-delivered report is reopened.

A load is delivered, and scale tickets are reconciled to the dry-weight basis the mass balance runs on.

Decide

A pool is built at the elevator, and each farm's attestation is listed as present or still open.

A load of non-North American origin arrives, and it is marked out of the pool for post-2025 production.

Out

A report is assembled, and it is stamped with the rule version and GREET release it was built against.

Execute write actions only inside the approval boundaries agreed during implementation.

→ Product statement

The agent assembles the documentation; a named producer attests, and the fuel producer registered under section 4101 claims the credit.

Example workflow

One load, field to report

AgentHuman

1Delivery recordedFarm record, agronomy platform, scale ticket or practice log

2Practice assembledNutrient budget, tillage passes, cover crop and soil tests, each with its source

3Report draftedPractice records, mass balance, open gaps and confidence

4Controls appliedNutrient-management checks, soil-test currency, dry-weight reconciliation and confidence threshold

No human action required

Stages 1 to 4 run unaided, and nothing is attested at any of them — the agent is assembling, and the originator's lane opens at the confidence gate.

5DecisionBranches at the confidence threshold

High confidence

Goes to the grain originator to release.

Low confidence

Adds an agronomy read first.

Originator release

The report is held with its practice records, its open gaps and the confidence.

Release · Amend · Send to agronomy review

Released — sent to the refiner▼

6Farm records updatedOnly where write access and approval policy allow it

7Outcome evaluatedGap closure, verifier queries, rejected fields and post-delivery corrections

Amendments

Every amendment made at release is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Signing the farm producer attestation.

Determining or petitioning for an emissions rate.

Making any representation on a producer's tax return.

Attesting at aggregation under penalty of perjury.

Automation boundaryAgent acts unaided

✓Assemble the field practice records behind a delivered load for the named owner.

✓Carry each record forward with the source it came from.

✓Apply the record formats and currency windows in force.

✓Mark the gaps the originator should weigh, and hold the report.

Any write happens inside the boundaries agreed at implementation, never ahead of release.

Committing a field to no-till in future years.

Issuing an LCFS verification statement.

Deciding which programme an acre is enrolled in.

Changes to practice, format or release rules.

Example output

One delivered load, annotated

Everything the agent assembles is attached to the record it was drawn from.

Feedstock report output · single loadIllustrative example

Load

Practice recorded

Dry weight

Source of record

Confidence

Attestation status

Corn, farm delivery

No-till on the delivering field, with a nutrient budget on file

58,400 lb dry

Farm record on file

89%

Producer attestation signed

As receivedTaken from the farm record and the scale ticket on file — nothing on this side is asserted by the agent.

Records gathered Nutrient budget on file Soil test within 2 years Scale ticket, dry basis

Why this recordIt records what the field did; 45Z is still a proposed rule, so nothing here is priced yet.

ActionReleaseAmendSend to agronomy review

What the score decidesBelow the configured threshold the report picks up an agronomy 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 delivered loadFrom the farm record

03Assembly

Assemble from the record

Draw on the field records on file and the formats USDA's final rule of 29 June 2026 sets.

01Approved path

You document, they claim

Routine loads arrive with their practice records already gathered.

02Human review

Send review to the thin fields

Open gaps and low-confidence reports are marked, so the originator's read starts where the record is thin.

04Build an evidence trail

The field, the practice recorded on it and the producer who attested stay on the load.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

Farm and agronomy recordsJohn Deere Operations Center
Climate FieldView · Granular

Grain and scale systemsBushel · AgriDigital
Cultura · Agris · Greenstone

Sustainability platformsTruterra · Regrow
Continuum Ag · Verity Tracking

Agent

Feedstock CI documentation

Reads the field
Assembles the report
Holds for release

Models and registries45ZCF-GREET · FD-CIC
CARB LCFS Reporting Tool

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the report

Six layers deep, each inside the one before. What still gets past is listed in the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeDrop assembly to record collection when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt, rule-version and GREET-release changes.Track

L4TraceabilityRecord the field records, the gaps, the amendments and the release time.Record

L3Originator releaseHold reports for the named originator; it governs release, not whether the records are right.Gate

L2Policy guardrailsTest reports against configured formats, currency windows and rule versions; a failure returns it.Restrict

L1Confidence thresholdsRoute low-confidence reports to an agronomy read before the originator sees them.Require review

Model coreReport assembled — practice records, mass balance, open gaps and confidence

L1 – L2Test whether a report may stand

L3Puts the release in the originator's hands

L4 – L5Keep the field and the practice behind it

L6Drops to record collection when signals degrade

How Nestack evaluates it

Evaluate the whole assembly — not only the finished report.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the report the refiner receives

Depth of coverage ▼

E1Final-output evaluationDid every practice record trace back to a field record?

E2Step-level evaluationDid the agent use the right rule version, GREET model and currency windows?

E3Tool evaluationDid it read and write the correct field and the correct season?

E4Confidence calibrationDo low-confidence reports actually attract more amendments?

E5Slice evaluationHow does performance change across specific field types?

E6Business outcomeHow many reports needed an amendment, or a correction after the load had gone?

Floor — the documentation the originator answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, placed at the stage each one originates.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

ZF-03

Superseded practice record

Practice read to an interim-rule field definition.

Stage gathersField records, tickets, tests and rule versions

02 · Reasoning2 modes

ZF-04

Nutrient budget assumed

A field passes on tillage with no budget on file.

ZF-06

Wet-weight mass balance

Scale weight used where dry weight is required.

Stage proposesPractice records, mass balance and confidence

03 · Tool / write2 modes

ZF-02

Estimate read as a score

A modelled input is passed on as a CI score.

ZF-05

Stale soil test carried

A test outside the two-year window moves on.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

ZF-01

Attestation gap at handoff

The first aggregation point never signed its attestation.

Stage returnsThe report the originator releases to the refiner

05 · Change / Version1 mode

ZF-07

Silent version regression

A rule or model change alters what the report accepts.

Stage tracksModel, prompt, rule versions and GREET release

Sev-1 · report released outside the boundary Sev-2 · a wrong record reaches the refiner Sev-3 · source degrades, report goes to review

See the complete Agriculture failure-mode catalogue →

Affected slices

Whole-farm completeness can hide one field

A farm-wide record-completeness score can look acceptable while a small number of field cohorts carry most of the gaps. Nestack reports the open-gap rate by slice, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Multi-farm aggregation pools	7.9%	3.7×	Review
Rented ground, split operators	6.3%	2.9×	Review
Fields under a second programme	3.9%	1.8×	Watch
Single-operator owned fields	1.1%	0.5×	Normal

Bar: open-gap-rate lift vs. single-operator-field baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

Nothing closes until a test exists

A cycle closes when the unsupported practice claim is a case the next release must pass. That is what the next load is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Open-gap rate rises in a field slice.

02Diagnose

The truckload that arrived without the field behind it is traced back, load by load, until one cause survives.

03Improve

The fix gets a number, and the loads that raised it are held against that number.

04Verify

No release while a touched practice case is outstanding; it reruns until green.

05Learn

The case stays for good, and the model version it was found against is recorded.

Learn → DetectThe return edge. The next load is documented 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, report assembly, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Delivery-load discovery and documentation boundary work.

02Farm-record and grain-system assessment.

03Practice-record, format and currency-window mapping.

04Field-record ingestion and normalisation.

05Report assembly and record binding.

06Confidence scoring and gap routing.

07Originator release workflow.

08Farm and grain-system integration.

09Practice and mass-balance cases.

10Guardrails and documentation controls.

11Load-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final 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 tier PilotOne farm, one elevator ProductionProduction farm records AdvancedMultiple elevators / regions

Introduced at Pilot

Assembly to your records and rules✓✓✓

Originator release✓✓✓

Record-completeness baseline✓✓✓

Introduced at Production

Reporting by field—✓✓

Release workflow in your systems—✓✓

Approved write-back—✓✓

Farm-record integration—✓✓

Introduced at Advanced

Multi-programme rule sets——✓

Multi-stage originator approvals——✓

High delivery volume——✓

Multi-programme documentation controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval 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 field records and delivery tickets → Field-record ingestion and practice mappingWeek 1

02Representative delivered loads → Assembly baseline, record indexing and source bindingWeek 2

03Your programme rules and the refiner's report format → Practice, format and currency mappingWeek 1

04Access to relevant APIs, feeds or exports → Farm-record and grain-system assessment, then integration setupWeek 2

05Loads you would not want audited → Verification cases and failure-mode testingWeek 4

06What no attestation may assert → Confidence scoring, gap routing, guardrails and release controlsWeek 3

07A named grain originator to release reports → Originator release workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

The weeks are drawn from the harvest, so the fifth carries evaluation and the pilot together.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Load discovery, rule mapping and the automation boundary W2Farm-record integration and the assembly baseline W3Report assembly, confidence logic and release controls W4Evaluation suite, currency checks and failure-mode testing W5Grain-system integration, pilot loads and targeted corrections W6One harvest delivered under the grain originator, then Agent Care handover

Reading the bandA band sits only on the weeks its work is named in. The week 5 overlap is real, not padding.

At the end of W6Validation closes on live loads and Agent Care picks up monitoring.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Agriculture AI agent

Build a CI documentation agent around the report your refiner needs.

Show us your field records and who releases to the refiner. Your agronomist signs that the budget fits the field — and DOE has not yet wired the USDA practices into 45ZCF-GREET.

Discuss this agent →

Nestack Agents · Feedstock CI & 45Z documentationAGT-AGR-19 · Agent Care available after launch