Assemble the FMVSS applicability and evidence matrix for a build, draft the Part 567 label content and the Part 555 petition, and hold the file for the engineer who certifies.
A standard applies, and the matrix is built from the vehicle type and the ratings on the base label.
02
A build is altered, and the matrix is re-run when the work moves GVWR or GAWR across a threshold.
Reason
03
A chassis arrives, and its Part 568 incomplete vehicle document is parsed standard by standard.
04
A standard the IVD makes no representation on is surfaced as work the final stage now carries.
05
A date is elected inside the window Part 568 allows, and the FMVSS edition it lands on is named.
Decide
06
A label is drafted to the Part 567 wording for the certifying party — alterer, intermediate or final stage.
07
A standard cannot be met, so a Part 555 petition is drafted against § 555.7(g) as amended 31 July 2026.
Out
08
A file is retained with its matrix, its evidence, the drafted label and the engineer who certified.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles and drafts; a named engineer reaches the compliance conclusion and affixes the label, under the reasonable-care standard in 49 U.S.C. § 30115.
Example workflow
One build, chassis to label
AgentHuman
1Build receivedChassis record, IVD, order specification or alteration work order
2Applicability determinedVehicle type, GVWR and GAWR, the standards in scope and the edition dates they carry
3Evidence reconciledTest reports, supplier statements, the IVD chain and confidence
Stages 1 to 4 run unaided, and no label is affixed at any of them — the agent is assembling a file, and the engineer's lane opens at the confidence gate.
5DecisionDivides at the confidence threshold
High confidence
Goes to the engineer to certify.
Low confidence
Adds a compliance review first.
Engineer certifies
The file is held with its matrix, its evidence and the standards left open.
Certify · Return to build · Escalate to compliance
Certified — released to the file▼
6Build systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedScope accuracy, returned builds, evidence gaps and post-delivery information requests
Returns
Builds sent back for evidence are counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Affixing the certification label to the vehicle.
Concluding that the build conforms to a standard.
Deciding which standards the alteration affected.
Signing or submitting a Part 555 petition.
Automation boundaryAgent acts unaided
✓Build the applicability matrix from the type,.
✓Parse the Part 568 IVD chain and surface the standards.
✓Draft the Part 567 label content for the certifying party to read.
✓Name the standards with no evidence behind them and hold the file.
Any write happens inside the boundaries agreed at implementation, never ahead of the label.
Electing the date the build is certified to.
Judging whether a device may be made inoperative.
Whether Part 566 identification reaches this shop.
Changes to standard sources or evidence rules.
Example output
One altered build, annotated
Everything the agent assembles is attached to the build it was drawn from.
Certification file · single buildIllustrative example
Build
Alteration
Label scope
Standard of record
Confidence
Statement
Accessible van conversion
Floor lowered, raised roof and a lift fitted
Standards affected only
FMVSS in effect, March 2026
91%
Drafted for the alterer to affix
As receivedTaken from the work order and the base vehicle's certification label.
Evidence assembledBase vehicle labelAlteration work orderStructural test report
Why this standard appliesThe lowered floor moved the seating reference and a person still decides.
ActionCertifyReturn to buildEscalate to compliance
What the score decidesBelow the configured threshold the file picks up a compliance review before 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 build that leavesFrom the build record
03Applicability
Work the delta, not the vehicle
Use the standards in force on the elected date, the base label's ratings and the IVD chain.
01Approved path
You certify yourself here
Nothing is filed and no agency clears the build first; § 30112 still bars the sale, so the file is the record.
02Human review
Send the read to the open standards
Standards with no evidence, and dates outside the permitted window, are marked so the engineer starts there.
04Build an evidence trail
The standard, the test it was met by and the engineer who certified stay on the build.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Standards and rulemakingeCFR · Federal Register NHTSA dockets · interpretations
Test and evidenceTest-lab reports · CAE Supplier conformity statements
Build recordsERP · MES · work orders Bills of material · VIN records
Agent
Homologation & FMVSS certification
Reads the build Builds the matrix Drafts the label
Document controlIVD and label archives PLM · quality systems
A line-wide coverage figure can read well while one build configuration carries nearly every standard left unevidenced. Nestack reports the unevidenced-standard rate by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Multi-stage ambulance builds
7.6%
3.5×
Review
Accessible van conversions
6.3%
2.9×
Review
GVWR-threshold alterations
3.8%
1.8×
Watch
Single-standard alterations
1.8%
0.8×
Normal
Bar: unevidenced-standard lift vs. single-standard baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends with one more standard case
A cycle closes when the undocumented standard is a case the next release has to catch. That suite is what the next build certified is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Unevidenced-standard rate rises in one configuration.
02Diagnose
The upfit that left the floor with a label and no file behind it is traced back to the standard nobody scoped.
03Improve
The correction ships numbered, with the builds that prompted it attached.
04Verify
Nothing ships while a touched standard case is failing; it runs until it clears.
05Learn
It is kept as a standing case, and the standard rules are revised alongside.
Learn → DetectThe return edge. What follows is measured against a suite that grew by one.
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, applicability logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Certification workflow discovery and boundary setting.
02Build-record and evidence assessment.
03FMVSS applicability, edition and evidence mapping.
04Build-record ingestion and normalisation.
05Applicability logic and edition pinning.
06Confidence scoring and gap routing.
07Engineer certification workflow.
08Build-record and PLM integration.
09Standard and evidence cases.
10Guardrails and labelling controls.
11Build-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 configuration, one siteProductionProduction build systemsAdvancedMultiple sites / product lines
Introduced at Pilot
Matrix on your standards and builds✓✓✓
Engineer certification✓✓✓
Standard-coverage baseline✓✓✓
Introduced at Production
Reporting by configuration—✓✓
Certification workflow in your systems—✓✓
Approved write-back—✓✓
Build-record integration—✓✓
Introduced at Advanced
Multi-standard exemption rules——✓
Multi-stage build approvals——✓
High build volume——✓
Multi-standard 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 build records and configuration structure→Build-record ingestion and evidence mappingWeek 1
02Representative certified builds→Applicability baseline, edition pinning and evidence bindingWeek 2
03Your standard sources and test reports→FMVSS applicability, edition and evidence-rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Build-record and evidence-source assessment, then integration setupWeek 2
05Builds you would not want labelled→Alteration cases and the evaluation suiteWeek 4
06What no label may stand on→Confidence scoring, gap routing, guardrails and labelling controlsWeek 3
07Named engineers to certify the builds→Engineer certification 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
The phases sit on the weeks the build really occupies, and the fifth runs two at once.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Certification workflow discovery, standard mapping and the boundaryW2Source integration and the applicability baselineW3Applicability logic, confidence scoring and labelling controlsW4Evaluation suite, evidence-coverage checks and failure-mode testingW5Build-system integration, pilot builds and targeted correctionsW6One build series certified under the compliance engineer, then handover
Reading the bandA bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6The last checks clear on live builds and Agent Care picks up monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Automotive AI agent
Build a certification agent around the file behind your label.
Show us a build, your evidence sources and who affixes the label. Whoever finishes the vehicle carries the certification — the alterer and the final-stage manufacturer, not the chassis OEM.
