.mgx
An MGX twin is a versioned, compiled expression of one canonical MaterialGraph variant record. It carries the visual, technical, source, readiness, rights, and intelligence context a downstream surface is allowed to use.
Derived from product truth. Shaped by profile and rights.
Why it exists
Most downstream tools receive fragments: a low-resolution image here, a stale PDF there, a few untyped fields in a feed. None of that is enough to render a material, answer responsibly, or explain what source supports a claim.
.mgx packages the reviewed record into a rights-aware, profile-aware twin. It does not replace the graph; it is a distribution surface for a specific consumer, use case, and permission set.
The pitch
The governed twin that makes product records portable.
Not another data feed. A governed record contract that can carry assets, specifications, sources, readiness, and capability hints without exposing private source bundles.
Inside the twin
Each twin is derived from the canonical record, then scoped by the requesting profile and asset rights state. Public fields, signed asset references, licensed links, and capability hints can vary without changing product truth.
How the material looks.
Approved imagery, render assets, physical-capture source, scale, repeat, and render metadata exposed only when rights allow.
What the material is.
Typed block values for dimensions, composition, compliance, fire performance, sustainability, acoustics, and other applicable product facts.
Where the record comes from.
Public source summaries, attribution, source links, freshness, confidence, and missingness without leaking internal traces or restricted payloads.
Where the twin can be used.
Profile-scoped eligibility for rendering, catalogue display, specification workflows, and agent answerability.
What machines can do with it.
Question-class answerability, capability hints, and retrieval context derived from canonical graph state.
Visual. Technical. Sources. Readiness. Intelligence.
Compiled for a surface
A canonical variant record is assembled from reviewed values, source, assets, observations, gaps, and projections.
The requesting profile and asset rights state decide which public fields, signed references, licensed links, and capability hints can travel.
MaterialGraph compiles a versioned .mgx twin for a specific consumer surface without changing canonical product truth.
Distribution surfaces
canonical record → profile + rights → .mgx twin → consumer surface
Who benefits
Consistent distribution without losing control of rights, attribution, or reviewed product truth.
Reliable product data, realistic visualisation, and explicit readiness or missingness before a product enters a workflow.
Structured twins that answer only inside declared source, freshness, readiness, and profile constraints.
Render-ready assets with the scale, repeat, rights, and representation-fidelity signals needed to show the material responsibly.
Built for agent consumers
Can I use this finish in hospitality?
What is the fire and VOC story here?
Show this textile on that chair.
Find similar options with lower embodied carbon.
Why this matters for brands
Your materials already exist in dozens of places, catalogues, distributor feeds, specification tools, sample libraries. Each one with different data, different images, different levels of completeness.
The .mgx twin is not the source of truth. It is the compiled expression of reviewed graph state for the surface that needs to render, answer, compare, export, or publish a product variant.
materialgraph.mgx
{
"format": "materialgraph.mgx",
"version": "0.1.0",
"identity": { "brand": "...", "variant": "..." },
"profile": { "id": "..." },
"rights": { "assetState": "..." },
"visual": { "assets": [...], "render": {...} },
"technical": { "blocks": [...] },
"sources": { "sourceRefs": [...], "sourceFactCount": 42 },
"readiness": { "render": "...", "answerability": [...] },
"intelligence": { "capabilities": [...], "retrieval": {...} }
}