01
Stable Product Types
Fields have purpose, type, identity, revision, and rule binding instead of being loose JSON keys.
Solution · Configurable products
Model a product once, then let every surface use the same definition.
ConfigAI separates product semantics from UI forms and application code. Product Types define what a product can contain; exact revisions preserve what those semantics meant when a configuration was created.
02
Products & components
Families, products, variants, components, assets, and relationships can coexist without assuming one industry shape.
03
Rules on reviewed fields
Configuration logic references approved field identities and revisions rather than UI labels.
Common product language
Flexible does not mean schema-less.
A completely free-form database is hard for both configurators and agents to reason about. ConfigAI uses a common product language with semantic field identities and optional sector-specific structures.
Field identity
Stable semantic key, display purpose, data type, cardinality, and revision.
Options & values
Explicit enumerations, references, ranges, units, defaults, and source-backed allowed values.
Components & relations
Products can contain or reference parts, modules, families, and compatibility relationships.
Assets
Images, documents, 3D models, and source evidence attach to the product revision they support.
Semantic revisions
Changing a field meaning is a migration decision.
A label change is not the same as changing what a field means. ConfigAI should preserve exact semantic revisions so saved configurations and rules can be reopened safely.
Field revision v1
width means overall product width in millimeters.
Historical
Proposed revision v2
source indicates width should represent seat width instead. Preview flags semantic impact.
Review
Migration choice
Reviewer decides whether to introduce a new field, migrate existing values, or reject the proposal.
Human gate
Exact reopen
Old configurations keep their original field revision while new configurations use the approved revision.
Versioned
Catalog-only is valid
Not every product needs 3D, rules, or pricing.
ConfigAI should support simple catalog products and complex configurable systems in the same workspace. Advanced capabilities attach only when the product actually needs them.
Catalog product
Identity, description, images, source data, and typed product fields.
Base
Configurable product
Adds options, compatibility, derived fields, and rule inputs.
Optional
3D-enabled product
Adds reviewed model revisions, semantic parts, and later digital-twin representations.
Optional
Commercial / production
Pricing, BOM, and ERP outputs attach as later layers instead of defining the base product model.
Roadmap
ConfigAI
A product model that can grow without being rebuilt.
Start with the minimum product semantics you need today and add rules, 3D, commercial, or production layers without creating a second source of truth.