
Regulatory facts are unusually dangerous to simplify. A small change in wording can change what a regulatory record appears to establish.
For medical products, AI must do more than find an FDA record. It has to determine which product the record belongs to, what regulatory pathway it represents, and what the record actually establishes.
Finding an FDA record is only the first step
An AI answer may discover an authoritative FDA record containing a real manufacturer name, device name, submission identifier and decision. That is useful evidence.
But several questions remain:
- Is this the exact product being discussed?
- Is it the same model or revision?
- What regulatory pathway does the record represent?
- What scope does the decision cover?
- Is the AI describing that scope accurately?
Retrieval alone does not answer these questions.
Regulatory language cannot safely be flattened
Words such as cleared, approved, authorized, registered and listed are not interchangeable labels for a generic state called "FDA certified." They can represent materially different regulatory concepts.
An AI system that retrieves the correct underlying record but translates its meaning into the wrong regulatory language has not invented the source. It has changed its meaning.
This is an important class of AI product error because the answer can look unusually credible. There is a real government record behind it. The identifier may be real. The manufacturer may be correct. Only the relationship or interpretation is wrong.
Product identity comes before regulatory interpretation
The safest structure is not:
Brand → FDAIt is more explicit:
Manufacturer → Product → Model / Revision → Regulatory Pathway → FDA Record → Scope / EvidenceThat structure prevents a decision associated with one device from silently becoming a statement about an entire product family. It also preserves lifecycle distinctions when products, models and regulatory records change over time.
AI creates a new propagation surface
Traditionally, regulatory teams controlled carefully worded documentation. Marketing controlled product claims. Product teams controlled specifications.
Those organizational boundaries do not exist inside a buyer's AI question. A user can ask is this device FDA approved? and an AI system may attempt to resolve product identity, regulatory history and the meaning of the record in a single answer.
That makes regulatory Product Truth a downstream AI problem as well as an internal compliance problem.
The goal is not to teach AI every regulation
The infrastructure problem is more fundamental. AI needs access to explicit relationships showing which product, which regulatory record, which scope, supported by which evidence. Then the interpretation can be measured against the authoritative record.
This is also why AI Product Truth should not replace regulatory systems. It should connect them.
The manufacturer remains authoritative for manufacturer Product Truth. FDA remains authoritative for the regulatory records it maintains. The missing layer is the machine-readable relationship between those worlds.
For regulated products, knowing the right fact is not enough. AI must know exactly which product the fact belongs to and what the authority actually said.