Product anchoring means fixing a virtual object to a real-world surface so it stays put as the viewer moves. This page records what XOM ships in that space today and what still has to be specified, because the anchoring layer itself is not present in the reviewed codebase.
01What XOM renders today
XOM's content model is a container framework: a routing component reads a post record from Realtime Database, takes its type and metadata, and lazy-loads a matching container component. Twenty-seven-plus container modules exist across six families — collaborative, dynamic, element, external, intelligent, and programmable.
The closest module to three-dimensional content is the dimensional container. It reads a model URL from the post's metadata field and renders that URL inside a full-screen-capable iframe labelled "3D Model Viewer". Everything a real anchoring system would own — camera, scene graph, plane detection, pose tracking — sits inside whatever viewer is on the other end of that URL, not inside XOM.
Products themselves do exist in the platform, but as a reward type rather than a catalogue. rewards/products is one of fifteen reward categories, covering physical and digital product rewards, and the marketplace that would sit above it is listed as planned rather than built in the platform's own revenue-stream table.
02What is not defined yet
A documented anchoring system needs four decisions that no reviewed source makes:
- The tracking source. Marker-based anchoring, device plane detection, or geospatial anchoring are different products with different hardware requirements.
- The anchor record. What is stored when a user places an object — an identifier, a pose, an owning account, an expiry — and whether it is shared or private.
- The product link. Which catalogue an anchor points into, and what happens when that record changes or is withdrawn.
- The client. XOM builds as a Next.js static export served over Firebase Hosting. There is no native application and no AR session layer in the code reviewed, so the runtime that would hold an anchor is undetermined.
03A note on the wider estate
Anchoring may not belong to XOM at all. The DigiFX platform roster lists OASIS RelicVerse as an immersive geo-based platform, and the shared platform authentication matrix records it under a geo-AR heading. If anchoring is intended as a shared capability across platforms rather than an XOM feature, that relationship should be stated before this page is published.