Brand customization covers the three places a business can shape how it appears inside XOM: its public brand profile, the creative it runs through the ad system, and the interface theming system that governs palette and cosmetic presentation.
01Brand profiles and handles
XOM maintains a handle registry (lib/accounts/handles.ts) that maps an account UID to a public, indexable handle. Each registered account carries a display name, avatar, verified flag, tagline, bio, website, and a sameAs list of external social profiles. The registry is deliberately additive and allowlist-based; the file notes that later phases will add personal, brand, and vendor accounts, either as further registry entries or resolved dynamically from the user records.
Every registered handle is pre-rendered as a static profile page at /{handle}. The page generates its own metadata — title, description, canonical URL, and social image — and emits JSON-LD for the organization, the website, and the profile. In practical terms, a registered brand gets a crawlable, structured profile page rather than a view that only exists inside the app shell.
02Creative control in the ad system
For advertisers, customization happens at the creative level. Each ad creative in the Ad Manager carries an editable title, description, media type (image, video, or a directory the engine samples from on each render), media URL, call-to-action label and destination, industry category, and a source flag distinguishing internal DigiFX creatives from external vendor creatives. Vendor creatives additionally carry a vendor name. Targeting is expressed as user types, interests, and geographies.
The directory media type is worth calling out for brands running longer campaigns: pointing a creative at a folder lets the ad engine pick a different asset from that folder on each render, which rotates creative without requiring a new campaign entry per asset.
03Interface theming
XOM's theme system defines each theme as a named record with a palette rather than a stylesheet. A theme carries an id, name, description, preview image, category, style, rarity, unlock requirements, availability, feature list, and a palette block with named tokens — background base, primary accent, secondary accent, highlight glow, UI edge light, overlay tint, primary text, and muted text. The default theme, "The Next Chapter", is free and uses XOM's own accent color; other themes are unlocked by level or purchased with platform currency. A parallel skins system covers narrower cosmetic changes.
That token structure is what makes theming portable: a theme is data, so adding one is a record, not a code change. Note that theming is currently a user-facing personalization system driven by progression and purchase, not a brand-supplied white-label mechanism.