Answer parameter and compatibility questions from the datasheet revision on file, cite that revision on the face of the answer, and hold it for the named applications engineer, who decides what is said.
Do not read the aggregate citation figure on its own — break it out by cohort. Nestack reports the rate by slice, because a few part families absorb most of the wrong answers.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Parts under an active PDN
6.5%
3.8×
Review
Suffix variants of one base part
4.4%
2.6×
Review
Optional-feature standards
3.2%
1.9×
Watch
Mature parts, one revision
1.2%
0.7×
Normal
Bar: wrong-citation lift vs. the mature-part baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends in the suite, not a meeting
The loop shuts when the miss is a case in the suite, not when it has been explained. That suite is what the next compatibility answer is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Wrong-citation rate rises in a part family.
02Diagnose
Read the released answers back against the revisions they cited, until one document, rule or prompt accounts for it.
03Improve
Whatever changes ships against a version, with the answers that prompted it attached.
04Verify
Nothing ships until the affected cases pass a second time.
05Learn
The suite grows by one case; so does the citation rule set.
Learn → DetectThe return edge. The next detection runs against a longer suite than this 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, citation workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Enquiry workflow discovery and boundary definition.
02Document source and revision assessment.
03Citation, suffix-resolution and certification mapping.
04Document ingestion and revision tracking.
05Citation logic and suffix resolution.
06Confidence scoring and refusal routing.
07Engineering release workflow.
08Product-data and PLM integration.
09Revision-currency cases.
10Guardrails and citation controls.
11Answer-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 product familyProductionProduction document sourcesAdvancedMultiple catalogues / regions
Introduced at Pilot
Citing to your document set✓✓✓
Engineer release✓✓✓
Citation-accuracy baseline✓✓✓
Introduced at Production
Reporting by product family—✓✓
Release workflow in your systems—✓✓
Approved write-back—✓✓
Product-data integration—✓✓
Introduced at Advanced
Multi-vendor document rules——✓
Multi-stage engineering approvals——✓
High enquiry volume——✓
Multi-catalogue answer 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 part catalogue and document repository→Document ingestion and revision mappingWeek 1
03Your citation rules and approved source list→Citation, suffix-resolution and certification-check mappingWeek 1
04Access to relevant APIs, feeds or exports→Document-source and parametric assessment, then integration setupWeek 2
05Answers that cited the wrong revision→Currency cases and failure-mode testingWeek 4
06Where an answer stops being information→Confidence scoring, refusal routing, guardrails and release controlsWeek 3
07Named applications engineers to release answers→Engineering release 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 bands follow real work rather than a plan, so evaluation and pilot genuinely share the fifth week.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Enquiry workflow discovery, citation rules and the automation boundaryW2Document-source integration and the citation baselineW3Citation workflow, confidence logic and release controlsW4Evaluation suite, revision-currency checks and failure-mode testingW5Product-data integration, pilot enquiries and targeted correctionsW6A live enquiry queue answered under engineering, then handover
Reading the bandEach bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6Once the queue validates, Agent Care owns the running agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Electronics AI agent
Build a spec agent around your document set and your engineers.
Show us the parts you get asked about and the documents behind them. If you can name the engineer who releases an answer, we will map the citation workflow around them.
