Key each funded item to the requirement its project funding date fixes, hold the manufacturer and supplier evidence behind each certification, and hand the signer the gaps before they certify.
An item is funded, so it arrives with its project, its funding programme and the purchase order that bought it.
02
A cut-off passes, and each item on that project is re-read against the obligation date the customer supplies.
Reason
03
An item is classified as iron or steel, a manufactured product or one of the listed construction materials.
04
A certificate lands, and the step chain behind it is laid out link by link with the handler each link names.
05
A component cost is quoted, and it is read against the cost definition at 23 CFR 635.410, not invoice price.
Decide
06
An input is missing, so the position stays open and the supplier who owes the figure is named in the pack.
07
A waiver is relied on, so its version date, its comment window and its Made in America Office status are tracked.
Out
08
A pack is complete, so it is held for the signer the recipient contract names, with the open items attached.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles the file; a named person signs it. Procurement asks what arrived and whether it conforms — this page asks what a signature can rest on today.
Example workflow
One funded item, order to signature
AgentHuman
1Funded item identifiedSchedule of values, purchase order, submittal or supplier declaration
2Dates and rules matchedThe obligation date the customer supplies, the funding programme and the recipient contract
3Position draftedClassification, evidence chain, cost position and confidence
4Controls appliedEvidence-chain checks, cost-definition checks, waiver-version checks and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is certified at any of them — the agent is assembling, and the signer's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the authorised signer.
Low confidence
Adds a compliance read first.
Signer approval
The pack is held with its evidence chain, its open items and the confidence.
Approve · Amend · Send to compliance review
Approved — file released▼
6Project records updatedOnly where write access and approval policy allow it
7Outcome evaluatedGap-closure time, signer amendments, cut-off misses and post-signature disclosures
Amendments
Every signer amendment, and every later disclosure, is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Signing or issuing the certification.
Determining that a funded item complies.
Requesting a waiver, or predicting its outcome.
Inferring a component cost from a comparable part.
Automation boundaryAgent acts unaided
✓Map each funded item to the project date and rule the customer supplies.
✓Assemble the manufacturer and supplier evidence behind each item.
✓Build the cost position to the definition in the rule cited.
✓Name the missing inputs and who owes them, and hold the pack.
Any write happens inside the boundaries agreed at implementation, never ahead of the signature.
Deciding which event fixes the obligation date.
Releasing an item for permanent incorporation.
Disclosing non-compliant material to the recipient.
Changes to classification, threshold or waiver rules.
Example output
One funded item, annotated
Everything the agent assembles is attached to the document it came from.
Certification pack · single funded itemIllustrative example
Item
Position drafted
Cost position
Source of record
Confidence
Requirement applied
Signal cabinet
Assembled in the United States; component costs unreturned
Open — inputs missing
Mill and supplier declarations
88%
Manufactured product standard
As receivedTaken from the purchase order and the declarations on file — nothing on this side is inferred by the agent.
Evidence usedSupplier declarationMill test reportPurchase-order clause
Why it is still openA component cost is unreturned, so the position stays open for the signer to weigh.
ActionApproveAmendSend to compliance review
What the score decidesBelow the configured threshold the pack picks up a compliance read before it reaches the signer.
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 funded itemFrom the purchase order
03Assembly
Build from the documents
Work from the declarations on file and the project dates and rules the customer supplies.
01Approved path
The date fixes the rule
Routine items arrive already matched to the rule their project sits under.
02Human review
Send review to the open gaps
Unsupported inputs and low-confidence packs are marked, so the signer reads where the exposure sits.
04Build an evidence trail
The item, the funding date behind it and the person who certified stay on the file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Project and cost systemsViewpoint Vista · HCSS Sage 300 CRE · B2W
Funding-programme sourcesFHWA Buy America notices Recipient bulletins · forms
Supplier evidenceMill test reports · declarations Submittal and PO records
Agent
Domestic-content certification
Reads the documents Builds the pack Holds for signature
A package-level evidence-provenance figure can look acceptable while a few funding programmes absorb most of the unsupported inputs. 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
Lift vs. threshold
Status
EPA revolving-fund packages
8.4%
3.7×
Review
Waiver-dependent items
5.9%
2.6×
Review
Multi-tier assemblies
3.6%
1.6×
Watch
Federal-aid iron and steel
1.1%
0.5×
Normal
Bar: open-gap-rate lift vs. federal-aid iron-and-steel baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends when a test exists
A cycle is done when the unsupported certification has become a case the next release must pass. That suite is what the next item certified is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Open-gap rate rises in one funding programme.
02Diagnose
The item ordered under one rule and delivered under the next is read back to a single cause.
03Improve
Stamp the change; the items behind it are filed against that number.
04Verify
Each touched item case is run again, and one red stops the release.
05Learn
It stays a standing test, and the threshold rules move with it.
Learn → DetectThe return edge. The next detection runs 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, certification workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Certification workflow and automation-boundary scope.
02Project, cost and supplier source review.
03Funding-date, threshold and waiver-rule mapping.
04Item ingestion and document normalisation.
05Classification logic and evidence binding.
06Confidence scoring and gap routing.
07Signer approval workflow.
08Project and supplier-record integration.
09Threshold and waiver cases.
10Guardrails and signing 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 programme, one jobProductionProduction project systemsAdvancedMultiple programmes / recipients
Introduced at Pilot
Pack assembly to your rules✓✓✓
Signer approval✓✓✓
Evidence-provenance baseline✓✓✓
Introduced at Production
Reporting by funding programme—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Supplier-record integration—✓✓
Introduced at Advanced
Multi-recipient contract rules——✓
Multi-stage signing approvals——✓
High item volume——✓
Multi-programme certification controls——✓
Build priceFrom $5,000From $8,000Custom 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 funded jobs and their project dates→Item ingestion and funding-date mappingWeek 1
02Representative certification packs→Assembly baseline, evidence binding and cost build-upWeek 2
03Your recipient contract and its certification forms→Recipient-contract, threshold and waiver-rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Project, cost and supplier assessment, then integration setupWeek 2
05Certifications you would not want audited→Cut-off cases and the evaluation suiteWeek 4
06What no certification may take on trust→Confidence scoring, gap routing, guardrails and approval controlsWeek 3
07Named signers to approve the packs→Signer approval 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
Every band is drawn to the weeks that phase truly needs, and so week five carries a pair of them.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Certification workflow discovery, rule mapping and the automation boundaryW2Source integration and the assembly baselineW3Assembly workflow, confidence logic and signing controlsW4Evaluation suite, cut-off cases and failure-mode testingW5Supplier-record integration, pilot packages and targeted correctionsW6One funded package run under the authorised signer, then Agent Care handover
Reading the bandEach bar spans only the weeks its own work is named in. The week 5 overlap is real work, not padding.
At the end of W6When the certification file validates, Agent Care takes the agent on.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Construction AI agent
Build a domestic-content agent around the person who signs.
The date on the funding paperwork decides which rule an item is certified under, and one project carries several. Show us your funded jobs and the person who signs. The False Claims Act counts per claim, so each pay estimate on a false certification is another one.
