Attach each standard menu item to the recipe version its nutrient values were calculated from, mark the basis that has drifted, and hold the substantiation file for the two individuals who sign it.
An item is added, and § 101.11(a) reaches a chain of twenty or more locations.
02
A basis is chosen, and § 101.11(c)(1) allows databases, cookbooks or laboratory analyses.
Reason
03
A recipe is changed, and § 101.11(c)(2) wants preparation to adhere to the factors used.
04
A file is assembled, and § 101.11(c)(3)(i) wants the database name, version and version date.
05
An analysis closes, and § 101.11(c)(3)(i)(F) brings a responsible individual to sign.
Decide
06
An outlet serves the item, and § 101.11(c)(3)(i)(G) wants a signer employed there.
07
A guest asks for more, and § 101.11(b)(2)(ii)(A) sets the written nutrition information.
Out
08
A request arrives, and § 101.11(c)(3) allows a reasonable period of time, not a date.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles the substantiation file and tracks what has drifted. A responsible individual signs and dates each statement under § 101.11(c)(3) — one for accuracy, one for adherence.
Example workflow
One menu item, evidence to certification
AgentHuman
1Item evidence receivedRecipes, database printouts, laboratory worksheets or outlet preparation records
2Item context assembledThe item, its basis, the outlets offering it and the recipe version its values came from
3Substantiation evidence draftedThe items covered, the basis recorded, the gaps and completeness
4Controls appliedBasis-currency checks, outlet-coverage checks, written-information checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is certified at any of them — the agent is assembling, and the nutrition lane opens at the completeness gate.
5DecisionSplits at the completeness gate
Evidence sufficient
Goes to the responsible individuals to certify.
Anything thin
Adds a nutrition read first.
Nutrition review
The file is held with its items, its basis and the outlets behind them.
Certify · Append evidence · Send to nutrition review
Signed and dated — under § 101.11(c)(3)▼
6Recipe and menu records updatedOnly where write access and records policy allow it
7Outcome evaluatedBasis currency, outlet coverage, reviewer corrections and what the read found
Corrections
Each nutrition correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Signing the accuracy statement, § 101.11(c)(3)(i)(F).
Signing the adherence statement, § 101.11(c)(3)(i)(G).
Certifying that a nutrient analysis is complete.
Deciding a chain is not a covered establishment.
Automation boundaryAgent acts unaided
✓Hold every menu item against the recipe version used.
✓Track the outlets where a standard menu item is offered for sale.
✓Mark each item whose basis has drifted since signing.
✓Assemble the evidence a request under § 101.11(c)(3) would reach.
Nothing is signed or certified except by a responsible individual, inside agreed limits.
Judging what a reasonable period of time allows.
Telling FDA the substantiation file is complete.
Setting the basis a menu item is declared from.
Changes to recipes, menu boards or file records.
Example output
One menu item, annotated
Production runs within a reasonable period of time upon request under § 101.11(c)(3) — audit-readiness, not a clock; this record is what one standard menu item carries.
Item evidence · single menu itemIllustrative example
Menu item
Recorded as
Item class
Evidence of record
Confidence
Held for
Grilled chicken bowl, § 101.11(b)(1)
Declared from the recipe version on file, basis current
Standard item
Database printout, 3 August 2026
Held uncertified
A responsible individual at each desk
As receivedTaken from the chain's own recipe files and database printouts — it reaches as far as those sources do.
What the record holdsRecipe of recordDatabase versionOutlet adherence
Why no certification hereWhether the file may be certified is a § 101.11(c)(3) act left to a person.
ActionCertifyAppend evidenceSend to nutrition review
What the score decidesBelow the configured threshold the file picks up a nutrition read before the signers see it.
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 menu itemFrom the recipe that sets it
03Evidence
Where the evidence is used
Our labelling and recipe helper owns what the pack declares and holds the artwork for the named label owner, while this page owns the menu board and the substantiation file behind it, with two different signers. Our drive-thru lane agent hands any allergen question to the shift team, and this page is what that shift team would have to have on file.
01Approved path
Two statements, two desks
§ 101.11(c)(3)(i)(F) may be signed at corporate headquarters or the parent entity; (G) only by a responsible individual employed at that covered establishment.
02Human review
What was checked, and not found
No Federal Register document amending § 101.11 in 2025 or 2026 was located, and the FDA menu labelling page still carries 13 December 2023; an eCFR marker reading last amended 8/19/2026 could not be reconciled against any published document, and Edition 2 of the supplemental guidance, announced 14 December 2023, remains draft.
04Build an evidence trail
The item, the nutrient basis under it and the individual who dated it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Recipe and menu systemsRecipe management · POS Menu boards and item files
Nutrient databasesDatabase name · version date Calculation worksheets
Laboratory analysesAnalytical method · worksheets Laboratory name and address
Agent
Menu substantiation
Reads the items Assembles the file Holds for the signers
Outlets and preparationStore systems · training Adherence records by outlet
Integration availability depends on the client's existing systems and API access.
Agent controls
Six reviews between the model and the signature
Six reviews, and not one of them repeats another. What clears every one is named in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the agent to evidence assembly when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and basis rules; no Federal Register amendment to § 101.11 was located for 2025 or 2026.Track
L4Item trailRecord each item, its basis, the outlets it reaches and every read of the file.Record
L3Signer releaseHold the file for the two responsible individuals; the hold governs release, not whether the analysis behind it was right.Gate
L2Basis guardrailsTest the evidence against § 101.11(b)(2)(ii)(A), (c)(1), (c)(2) and (c)(3); the supplemental guidance of 14 December 2023 is still draft.Restrict
L1Confidence thresholdsRoute a thin file to a nutrition read before either signer sees it.Require review
Model coreEvidence assembled — the item, the basis, the outlets and completeness
L1 – L2Test whether a file may stand
L3Puts the certification in a person's hands
L4 – L5Keep the item and the basis behind it
L6Holds the statement undrafted when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the substantiation file that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the file a request reaches
Depth of coverage ▼
E1Final-output evaluationDid the evidence record what each menu item actually rests on?
E2Step-level evaluationDid the agent read the right item, the right basis and the recipe version in force?
E3Tool evaluationDid it read and write the correct item record and the correct basis?
E4Confidence calibrationDo low-confidence files actually attract more nutrition corrections?
E5Slice evaluationHow does performance change across specific menu items?
E6Business outcomeHow many files needed a correction before the individuals signed?
Floor — the file the chain answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed at the stage where it first shows.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
JU-03
Stale recipe read
The recipe read is not the one the outlet now cooks.
Stage gathersThe items, the recipes, the basis and the dates
02 · Reasoning2 modes
JU-04
Item asserted, not shown
An item is called covered without its basis.
JU-06
Draft guidance read as final
The supplemental edition is worked as binding.
Stage proposesThe items, their basis and file completeness
03 · Tool / write2 modes
JU-02
Thin file passed forward
A file moves on without the nutrition read.
JU-05
Evidence bound to wrong item
A worksheet is filed against the wrong item.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
JU-01
Certified, basis unrecorded
The file shows a signature but not what supported it.
Stage returnsThe file a signer dates and a request would reach
05 · Change / Version1 mode
JU-07
Silent basis regression
A recipe change moves the values, not the file.
Stage tracksModel, prompt, basis rules and evidence fields
Sev-1 · a value posted on no basisSev-2 · wrong basis reaches the fileSev-3 · degraded source, file uncertified
An item-level substantiation-coverage figure can read clean while limited-time offers carry most of the rework. Nestack reports the correction rate by menu item, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Limited-time offers
6.8%
3.6×
Review
Items with supplier substitutions
4.9%
2.6×
Review
Build-your-own combinations
3.1%
1.6×
Watch
Core items unchanged for a year
1.7%
0.9×
Normal
Bar: correction-rate lift vs. core-item baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unsubstantiated value costs
The loop shuts when the unsubstantiated value is a regression case. That suite is what the next item posted is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on limited-time offers.
02Diagnose
The supplier substitution nobody told the desk that signed for the calorie count, and the board that kept posting the old number, are read back until one cause remains.
03Improve
Any change goes out numbered, with the items that caused it attached.
04Verify
One item case still failing is enough to hold the release back.
05Learn
One case joins the suite, one line joins the substantiation file.
Learn → DetectThe return edge. The next file is measured 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, evidence assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Menu-item discovery and automation-boundary work.
02Recipe, database and outlet sources.
03Item-to-basis and outlet-adherence coverage mapping.
04Item and basis evidence ingestion.
05Item, outlet and record binding.
06Completeness scoring and review routing.
07Responsible-individual signing workflow.
08Recipe and menu-system integration.
09Substantiation and outlet cases.
10Guardrails and statement controls.
11Item-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 chain, one menu cycleProductionProduction menu systemsAdvancedMultiple brands / menu sets
Introduced at Pilot
Evidence assembly to your items✓✓✓
Responsible-individual release✓✓✓
Menu-item inventory baseline✓✓✓
Introduced at Production
Reporting by outlet—✓✓
Signing workflow in your systems—✓✓
Approved write-back—✓✓
Recipe-system integration—✓✓
Introduced at Advanced
Multi-brand menu sets——✓
Cross-outlet evidence packs——✓
Large item registers——✓
Multi-outlet adherence controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, item register size, 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 covered establishments and the items they offer→Item inventory mapping and evidence captureWeek 1
02Representative recipes, database printouts and laboratory worksheets→Record binding, basis logic and the evidence baselineWeek 2
03Your reasonable basis under § 101.11(c)(1)→Item mapping, basis binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Recipe, database and outlet-source assessment, then integration setupWeek 2
05Items you would not want requested→Outlet cases and the evaluation runWeek 4
06What no nutrient statement may settle→Completeness scoring, review routing, guardrails and release controlsWeek 3
07Two responsible individuals to sign→Signing 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
These widths measure the work and not the page, which is why a single week has to carry two phases.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Menu substantiation discovery, item mapping and the automation boundaryW2Source integration and the basis-coverage baselineW3Evidence assembly, basis logic and release controlsW4Evaluation suite, outlet cases and failure-mode testingW5Record integration, pilot items and targeted correctionsW6One menu cycle run under the responsible individual, then Agent Care handover
Reading the bandA band sits only on the weeks its own work is named in, and the fifth of them holds a pair.
At the end of W6Once the substantiation file validates, Agent Care assumes the agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Food & Beverage AI agent
Build a menu substantiation agent around the file two individuals have to sign.
Show us one standard menu item and the recipe version its calorie count was calculated from. Send that item over and we will assemble the § 101.11(c)(3) file around it, accuracy routed to headquarters and adherence to the outlet. Pack declarations belong to a different agent.
