Skip to main content

Why Not a Data Product?

The distinction between Data Product and AI Product is not based on whether one is “static” and the other “dynamic”, nor on whether one retrains or drifts. Those are implementation/lifecycle characteristics and are not universal.

The stronger distinction comes from Product Intrinsic Nature (PIN):

Data Products productize governed data/business truth. AI Products productize governed artificial-intelligence capability.

They can depend on one another without becoming the same Product Family.


Value-bearing essence​

Product FamilyValue-bearing essenceEssential value capability
Data Productgoverned data / representation of business realityexpose trusted, governed data for consumption
AI Productgoverned artificial-intelligence capabilityinfer, reason, perceive, generate, plan, optimize or act intelligently

A Fraud Detection AI Product may consume a Payment Lifecycle Data Product, but the thing being productized is fraud-detection intelligence rather than payment data itself.

Likewise, an AI Product may emit data. That output can later be productized separately as a Data Product, but the originating AI Product does not become a Data Product merely because it produces data.


Dependencies do not determine family by inheritance​

The Data Product and Model Product are dependencies in the AI Product constitution. Their families do not automatically transfer to the resulting Product.

This is the same BPS/PIN rule used for other Products: a Movie produced with AI remains a Movie Product if the audiovisual work is the value-bearing essence; a streaming service using recommendation AI remains a Service Product if the service capability is the value-bearing essence.


Lifecycle characteristics are orthogonal​

The following are not reliable family discriminators:

  • real-time vs batch;
  • static vs dynamic;
  • learned vs deterministic;
  • retraining vs no retraining;
  • API vs stream;
  • cloud vs edge;
  • high vs low risk.

A Data Product may be real-time and continuously evolving. A symbolic AI Product may have learningMode = NONE. Therefore AIPS does not define AI Products by “drift and retraining”.


AI-specific governance still matters​

Once a Product qualifies as AI, AIPS adds AI-specific semantics including:

  • AI Qualification Evidence;
  • APT and intelligence provenance;
  • Intelligence Capability and Effect;
  • Agency / Autonomy;
  • Embodiment and Physical AI semantics;
  • R0-R4 effective risk and Governance Obligation Profile;
  • AI trust/currentness and assurance;
  • downstream requalification when intelligence dependencies change.

These obligations arise because artificial intelligence is the Product's value-bearing essence, not simply because data is processed dynamically.


Complementary Product families​

Data Products commonly provide governed inputs to AI Products. AI Products can also support the creation of Data Products, Information Products, Services and Compound Products.

The correct relationship is therefore:

complementary Product families connected through explicit constitution and dependency graphs — not one family treated as a subtype of the other.


Summary​

  • AI Product and Data Product are distinguished by what is being productized.
  • Data dependency does not make an AI Product a Data Product.
  • Data output does not make an AI Product a Data Product.
  • Dynamics, drift and retraining are not universal family tests.
  • PIN and current Product constitution provide the durable classification basis.