New

Google AI Mode and AI Overviews opened in Türkiye on 18 February 2026. Check how your brand shows up in those experiences in three minutes. Start the check →

MORFAXIS Glossary

So everyone uses the same term to mean the same thing

This glossary is a consistency instrument rather than a word list. Every page on this site uses a term as defined here, and the same definitions apply in proposals and reports.

Direct answer

The MORFAXIS Glossary gives 40–80 word definitions of brand system, 3D product experience and AI search visibility terms. Each entry also names the concept it is most often confused with in practice — most scope arguments in real projects start at exactly those points.

Each definition is 40–80 words and reads without context. The “commonly confused with” line names the concept it gets mixed up with in practice — most scope arguments in real projects start at exactly those points.

Brand and system

AI-native brand system

An operating model that unifies strategy, product knowledge, messaging, verbal identity, examples, constraints and approval flows into one structure usable by both people and AI tools. It rests on the structure of brand knowledge rather than a single tool, so the system survives a change of tooling.

Commonly confused with: An agency that uses AI. The difference is not tooling but who keeps the system.

Related page →

Brand knowledge base

The source where strategy, product data, message library, evidence records and constraints are held in one structure with an assigned owner for updates. Content production, sales material and AI tools all feed from it; a knowledge base without an owner goes stale within six months.

Commonly confused with: A brand guideline. A guideline defines appearance; a knowledge base defines information.

Related page →

Message architecture

The structure binding the primary message, supporting messages and channel-level variations together. In B2B it is never written as one layer: the primary message carries category and reason-to-prefer, while supporting messages are built per decision-maker role with their own evidence.

Commonly confused with: A slogan. A slogan is one sentence; message architecture is a set of decisions.

Related page →

Value proposition

A statement of who a company serves, which problem it solves, with what evidence, and why better than alternatives. It only works alongside the list of evidence requirements that hold the sentence up.

Commonly confused with: A mission statement. A mission looks inward; a value proposition looks at the buyer.

Related page →

ICP (ideal customer profile)

A definition of the customer type where the product creates most value, at the level of sector, scale, technical maturity, buying behaviour and triggering event. In B2B it describes a company, not a person; the person level is built separately as a buying committee map.

Commonly confused with: A persona. An ICP describes the company, a persona describes the individual.

Related page →

Buying committee

A map of the people involved in a B2B decision and the risk each of them weighs. In technical products this typically includes the managing director, production or operations manager, application engineer and procurement — each wanting different evidence.

Commonly confused with: A single decision-maker. Assuming one decider is a frequent cause of lost proposals.

Related page →

Brand governance

The rule set defining who updates brand knowledge, who approves which content, and which claim may be published with what evidence. In AI-assisted production it is the only mechanism that substitutes for review as speed increases.

Commonly confused with: Brand policing. Governance does not block; it writes down which route is open.

Related page →

3D and product

3D product twin

A visually verified digital counterpart of a product, ready for marketing and sales use: master model, material system, variant matrix and the imagery, animation and interactive outputs derived from them.

Commonly confused with: An operational digital twin. This distinction is the most critical line in scope and budget.

Related page →

Operational digital twin

A digital counterpart of a physical asset connected to sensor data, live operation and engineering systems. It targets work such as predictive maintenance and process simulation, and requires a different team, budget and technology stack from a marketing-oriented 3D product twin.

Commonly confused with: A 3D product twin. The boundary must be separated in writing before any proposal.

Related page →

Render

The conversion of a three-dimensional scene into a two-dimensional image using lighting, material and camera settings. In product marketing a render is an outcome; what determines quality is the model preparation and material calibration that precede it.

Commonly confused with: 3D modelling. The model is geometry; the render is a photograph of that geometry.

Related page →

PBR material

A physically based material definition describing how a surface actually reflects light, through parameters such as base colour, roughness, metallic value and normal maps. Because the same material behaves consistently under different lighting, it makes variant production scalable.

Commonly confused with: A texture. A texture is an image; a PBR material is a description of behaviour.

Related page →

Exploded view

A depiction of an assembly with its parts separated while their relationships are preserved. It delivers most value in service training, spare part communication and assembly guides, and is used in sales where internal quality drives the decision.

Commonly confused with: A cutaway. A cutaway slices through; an exploded view pulls parts apart.

Related page →

Kinematic animation

Animation where linked part movements are built to the logic of the real mechanism. Its accuracy depends on engineering sign-off; a wrong motion sequence is spotted in the sales meeting and damages technical credibility.

Commonly confused with: Free-form animation. Free-form looks attractive; kinematic looks correct.

Related page →

Polygon budget

The triangle count a 3D model must stay under to run smoothly on a target platform. For web scenes the typical target is under 250,000 triangles. A CAD model sits far above that budget, and simplification is a separate production step.

Commonly confused with: Model quality. A higher polygon count is not better — only heavier.

Related page →

GLB / GLTF

A 3D file format designed for web and AR that carries geometry, materials and animation in one package. GLTF is the text form, GLB the binary one. With Draco or Meshopt compression it is the standard for models that open quickly in a browser.

Commonly confused with: CAD formats such as STEP. CAD is for manufacturing; GLB is for display.

Related page →

CAD simplification

Stripping an engineering model of internal geometry irrelevant to explanation, regrouping the assembly tree and repairing surface errors. Skipped, the resulting image is technically correct but commercially unusable.

Commonly confused with: File conversion. Conversion changes the format; simplification reorganises the content.

Related page →

Configurator

An interactive experience where a visitor changes colour, material, size and module options in real time and sees the product in the browser. Built correctly, choices bind to valid variant rules and the output feeds a quotation or enquiry form.

Commonly confused with: A 360-degree viewer. A viewer shows; a configurator lets you choose.

Related page →

Variant matrix

The structure defining colour, material, size and module options across a product family, and which combinations are valid. Because imagery is derived from the matrix rather than shot individually, unit cost falls as variant count rises.

Commonly confused with: A product list. A list says what exists; a matrix says what is valid together.

Related page →

Search and visibility

SEO

The system for being crawled, indexed and ranked, and for winning organic demand. It covers technical accessibility, content quality, site architecture and authority signals, and it is the foundation AI search experiences build on — without it, nothing layered on top returns anything.

Commonly confused with: Content production. Content is one component of SEO, not the whole of it.

Related page →

AEO

The discipline of producing clear, short, verifiable answers to user questions. In practice it means asking the question explicitly in the heading and giving a 40–80 word answer directly beneath it that reads without context.

Commonly confused with: GEO. AEO is a content-form problem; GEO is a system problem.

Related page →

GEO / GSO

Optimisation so a brand's content is found, understood and treated as a source inside generative AI and AI search experiences. Beyond answerability it covers entity clarity, citability and third-party authority.

Commonly confused with: A replacement for SEO. GEO does not replace SEO; it is built on top of it.

Related page →

Entity clarity

Having a brand's name, category, description and contact details identical across every platform. It determines whether search and answer systems can place the brand in the right category; contradictory information makes confident description difficult.

Commonly confused with: Brand awareness. Awareness is volume; entity clarity is consistency.

Related page →

Citation

A piece of content being referenced in an AI answer for a specific fact. It is largely a matter of content quality, answerability and technical access, and can be advanced by work on your own site.

Commonly confused with: Recommendation. Citation is about information; recommendation is about purchase options.

Related page →

Brand mention

A brand's name appearing in a third-party source, with or without a link. It is the slowest but most decisive component of entering the evaluation set in AI answer systems; purchased mentions and fake forum posts create risk rather than value.

Commonly confused with: A backlink. A link is a technical signal; a mention is a contextual one.

Related page →

Schema.org / structured data

Markup that states a page's meaning explicitly to search and answer systems. The critical rule is that markup must match the visible content exactly; information present in schema but absent from the page is a risk, not an optimisation.

Commonly confused with: A ranking factor. Schema declares meaning; it guarantees no ranking.

Related page →

llms.txt

A proposed plain-text file that describes a site's structure and key sources to AI systems; support is not yet widespread. Google has stated plainly that it does not use the file for visibility, so it is a helper layer for systems that do support it.

Commonly confused with: robots.txt. robots.txt governs access; llms.txt offers a content map.

Related page →

Core Web Vitals

The three metrics Google uses to measure page experience: LCP (largest contentful paint), INP (interaction to next paint) and CLS (cumulative layout shift). They are not a separate AI-visibility requirement but the precondition of accessibility.

Commonly confused with: Page speed. Speed is one component; stability and responsiveness are measured too.

Related page →

Cannibalization

Two pages weakening each other's visibility by targeting the same search intent. The fix is not more content but a single-ownership rule: each primary keyword has one owner page and the others link to it.

Commonly confused with: Duplicate content. Duplication is a text problem; cannibalization is an intent problem.

Related page →

Go-to-market

Go-to-market strategy

The integrated planning and execution of positioning, target customer, messaging, channel, content and sales system decisions for a new product, category or country. It is not a campaign but a set of deliverables that must all be ready on the same date.

Commonly confused with: A launch campaign. A campaign announces; go-to-market builds the system.

Related page →

Distributor sales kit

An editable but locked material set that lets dealers and distributors sell without inventing their own material. Product narrative and imagery are fixed while contact and pricing fields remain changeable, accompanied by a short usage guide and objection answers.

Commonly confused with: A corporate deck. A deck explains; a kit sells.

Related page →

Specification language

The product description a project specification requires — capacity range, standards complied with, materials and test methods — published in copyable form. In building and mechanical systems it directly decides whether a product is considered at all.

Commonly confused with: A product description. A description persuades; specification text qualifies.

Related page →

When the terms are clear, so is the scope.

Most scope arguments start with two sides using the same word to mean different things.