Food & Beverage AI agent · Alcohol excise
Alcohol Excise & Operations AI Agent
Anchor every figure on the Brewer's Report of Operations to the record behind it under 27 CFR 25.297, run the return and report clocks, and hold the package for the proprietor who signs.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Named signer
- Under perjury
- After launch
- Agent Care
What this agent does
Assembles the evidence, never the declaration
In
- 01
A return period closes, and 27 CFR 25.164 leaves fourteen days to file and to pay.
- 02
A period runs semimonthly, and 27 CFR 19.235 sets that same clock on a spirits plant.
Reason
- 03
A reporting period ends, and 27 CFR 25.297 wants the brewer's report on the fifteenth day.
- 04
A gauge is taken, and 27 CFR 25.300 keeps its record at the brewery for three years.
- 05
A period is reconciled, and 27 CFR 24.300 holds the wine source records on the premises.
Decide
- 06
A record sits off-site, and 27 CFR 19.575 still wants it produced at the plant in two days.
- 07
A declaration is executed, and 27 CFR 19.45(b) wants the signature and the title on it.
Out
- 08
An import claim is assigned, and T.D. TTB-201 moved that deadline to 31 March.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent reconciles the period and ties each figure to its record. The proprietor or a duly authorized representative signs under penalties of perjury, giving signature and title.
Example workflow
One return period, records to declaration
- 1Period records receivedProduction, gauge, transfer-in-bond, removal and inventory entries
- 2Period context assembledThe permit, the period it falls in, the form it feeds and the clock already running on it
- 3Reconciliation draftedThe figures reported, the records under them, the variances and completeness
- 4Controls appliedClock checks, record-support checks, variance checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is declared at any of them — the agent is reconciling, and the excise lane opens at the completeness gate.
Goes to the proprietor or duly authorized representative to sign.
Adds an excise analyst read first.
Excise review
The package is held with its period, its variances and the records they rest on.
Sign · Append records · Send to excise review
Declared — under penalties of perjury
- 6Premises and filing records updatedOnly where write access and records policy allow it
- 7Outcome evaluatedRecord support, clock timing, analyst corrections and what the read found
Corrections
Each excise correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Signing the return under penalties of perjury.
- Declaring that records support the reported figure.
- Filing TTB F 5000.24 on a proprietor's own authority.
- Judging a variance between gauge and book.
Automation boundary
Agent acts unaided
- ✓Tie every reported figure to the record that already supports it.
- ✓Run the fourteen-day return clock and the report clock.
- ✓Chase the source record a reported removal still lacks before filing.
- ✓Flag the figure whose supporting record cannot be shown.
Nothing is declared or filed except by a named person, inside the agreed boundaries.
- Settling which return period a permit falls into.
- Telling TTB that a period is correctly reported.
- Certifying a claim as to authority and truthfulness.
- Changes to production, gauge or filing records.
Example output
One return period, annotated
Two clocks run apart on the same premises — fourteen days to the return, the fifteenth day to the report; this record is what one period carried between them.
Period evidence · single return period
Illustrative example- Return period
- Taxable removals, 27 CFR 25.164
- Recorded as
- Reconciled to gauge and removal entries
- Period class
- Semimonthly period
- Evidence of record
- Brewer's report, 3 August 2026
- Confidence
- Held undeclared
- Held for
- The proprietor or authorized representative
As received
Built from the gauge, transfer and removal entries the premises already holds, and no wider than those.
What the record holds
- Gauge record
- Transfer in bond
- Removal entry, dated
Why no declaration here
Executing the perjury declaration is reserved by 27 CFR 19.45(b) to a person.
What the score decides
Below the configured threshold the package picks up an excise read before the signer sees it.
Action
SignAppend recordsSend to excise reviewValue
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value lands
Value 01 – 04
Every return period
From the permit that owes it
Where the evidence is used
No other Food and Beverage agent touches a TTB permit or an excise return period, and label approval under 27 CFR 13.21 is a prerequisite gate on a launch, not one of these clocks.
The declaration covers the records
TTB F 5130.9 declares the report "supported by true, complete, and correct records that are available for inspection at my brewery" — the evidence base, not the arithmetic.
What was checked, and not found
The Federal Register API could not be reached, so TTB Notices 237 and 238 of 17 January 2025 stand as no final rule found rather than none existing; the perjury wording on TTB F 5120.17 and on the 5110 series was not read; and the Q1-2026 CBMA advisory sits in trade press alone, unconfirmed by TTB. State excise, brand registration and three-tier duties are dozens of separate regimes sharing no form, no deadline and no signer, which is why this page stays federal.
Build an evidence trail
The period, the operation reported in it and the proprietor who declared stay on file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Production and gauge records
- Brewhouse logs
- tank gauges
- Volumes produced and gauged
Transfers and removals
- Bond transfers
- shipping
- Taxable removal entries
Inventory and losses
- Cellar counts
- loss reports
- 27 CFR 25.300 record set
Agent
Alcohol excise and operations
- Reads the period
- Ties figure to record
- Holds for the proprietor
Permits and filing calendar
- Permit register
- myTTB
- Return and report clocks
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six passes between the model and the declaration
Six passes over the same period, each narrower than the last. What survives is set out in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a package may stand
- L3
- Puts the declaration in a person's hands
- L4 – L5
- Keep the period and the operation behind it
- L6
- Holds the return undeclared when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the package that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the package an auditor reads
- E1Final-output evaluationDid the package show what supports each figure reported?
- E2Step-level evaluationDid the agent read the right permit, the right period and the entries in force?
- E3Tool evaluationDid it read and write the correct period record and the correct figure?
- E4Confidence calibrationDo low-confidence packages actually attract more excise corrections?
- E5Slice evaluationHow does performance change across specific return periods?
- E6Business outcomeHow many packages needed a correction before the proprietor signed?
Floor — the record the premises answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed at the stage where it first shows.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- JO-03
Stale gauge read
The gauge read is not the one now on the tank.
Stage gathers
The permit, the period, the figure and the record
02 · Reasoning
2 modes
- JO-04
Figure asserted, not shown
A figure is reported without the entry under it.
- JO-06
Proposal read as duty
Notice 237 is worked as a live obligation.
Stage proposes
The periods, their figures and completeness
03 · Tool / write
2 modes
- JO-02
Thin package passed forward
A package moves on without the excise read.
- JO-05
Record bound to wrong period
An entry is filed against the wrong period.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- JO-01
Declared, record unshown
The filing carries a figure but not what supports it.
Stage returns
The package a proprietor signs and an auditor reads
05 · Change / Version
1 mode
- JO-07
Silent period regression
A configuration change moves the clock, not the record.
Stage tracks
Model, prompt, period rules and evidence fields
- Sev-1 · a return declared on no record
- Sev-2 · wrong figure reaches the filing
- Sev-3 · source degrades, return holds unsigned
Affected slices
Semimonthly beer periods absorb the corrections
A period-level reconciliation figure can read clean while semimonthly beer periods carry most of the rework. Nestack reports the correction rate by return period, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Semimonthly beer periods | 9.2% | 3.6× | Review | |
| Periods with transfers in bond | 6.6% | 2.6× | Review | |
| Quarterly wine premises periods | 4.1% | 1.6× | Watch | |
| Annual small-permit periods | 2.4% | 0.9× | Normal |
Bar: correction-rate lift vs. annual-period baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
What an unsupported figure costs
The loop shuts when the unsupported figure is a regression case. That suite is what the next period closed is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Correction rate rises on semimonthly beer periods.
- 02
Diagnose
The sentence above the signature that covers the records, not the numbers, is worked back over the period until one cause remains.
- 03
Improve
Any change goes out numbered, with the periods that caused it attached.
- 04
Verify
One period case still failing is enough to hold the release back.
- 05
Learn
One case joins the suite, one line joins the premises record.
Learn → Detect
The return edge. Each period after this one answers to 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, evidence assembly, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Return-period discovery and automation-boundary work.Week 1
- 02Production, gauge and removal sources.Week 1, Week 2
- 03Figure-to-record and period-clock coverage mapping.Week 1, Week 2
- 04Period record ingestion.Week 2
- 05Permit, period and record binding.Week 2, Week 3
- 06Completeness scoring and review routing.Week 3
- 07Proprietor declaration workflow.Week 3, Week 4
- 08Production-system integration.Week 5
- 09Reconciliation and period cases.Week 4, Week 5
- 10Guardrails and declaration controls.Week 4
- 11Premises-trail instrumentation.Week 5, Week 6
- 12Deployment, documentation and Agent Care handover.Week 6
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 permit, one year | ProductionProduction excise workflow | AdvancedMultiple permits / premises |
|---|---|---|---|
| Introduced at Pilot | |||
| Reconciliation to your periods | ✓ | ✓ | ✓ |
| Proprietor declaration release | ✓ | ✓ | ✓ |
| Operations-inventory baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by return period | — | ✓ | ✓ |
| Declaration workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Production-record integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-permit registrations | — | — | ✓ |
| Cross-form evidence packs | — | — | ✓ |
| Large premises estates | — | — | ✓ |
| Multi-permit period controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom quote |
- Final build price
- Confirmed after discovery based on integrations, workflow complexity, period volume, approval controls and deployment requirements.
- Separate from build
- Build 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 bring
We build with it
01Your permits and the periods they file on
→Permit mapping and period-record capture
Week 102Representative production, gauge and removal entries
→Record binding, clock logic and the reconciliation baseline
Week 203Your premises record set under 27 CFR 25.300
→Period mapping, record binding and the automation boundary
Week 104Access to relevant APIs, feeds or exports
→Production, gauge and removal-source assessment, then integration setup
Week 205Returns you would not want declared
→Period cases and failure-mode testing
Week 406What no operations report may settle
→Completeness scoring, review routing, guardrails and release controls
Week 307A proprietor or duly authorized representative to sign
→Declaration workflow, then pilot and production validation
Weeks 5–6
Nothing else is required
Deployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
What each bar spans is worked time and not drawn space, so the fifth week has to hold two of them.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Excise workflow discovery, period mapping and the automation boundary
W2Source integration and the reconciliation baseline
W3Record binding, clock logic and release controls
W4Evaluation suite, period cases and failure-mode testing
W5Filing integration, pilot periods and targeted corrections
W6One return year run under the plant proprietor, then Agent Care handover
- Reading the band
- Every bar here holds only the weeks its own work is named for. The fifth takes two, because the work does.
- At the end of W6
- Once the premises record validates, Agent Care assumes the agent.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Food & Beverage AI agent
Build an excise operations agent around the periods your permits already owe.
Show us one return period and the entries behind its figures. That declaration has to survive an auditor standing on your premises, because 27 CFR 25.300 leaves the supporting set there for three years. State excise and brand registration are not on this page.
- Typical delivery
- 4–6 weeks
- Deployment
- Your return periods
- Named signer
- Under perjury
- After launch
- Agent Care available
Nestack Agents · Alcohol excise
AGT-FB-15 · Agent Care available after launch