A trigger is a marker attached to content or state that causes something else to happen when a condition is met. XOM contains several distinct trigger mechanisms rather than one feature called Trigger Tags, and they operate at different layers of the platform.
01Access triggers
The most formally documented triggers in the estate are authorisation triggers. A shared authentication matrix records, for each platform, the conditions that begin an access decision and what is granted when the policy check passes. XOM's three entries are:
- A user session begins for a consumer, creator or moderator. The policy check consults community governance rules and moderation escalation thresholds; the grant is a session token carrying an anti-abuse risk score used for adaptive moderation.
- An XP, mission or leaderboard write is submitted. The check evaluates mission eligibility against region, age and licence constraints; the grant is a write-protected reward wallet nonce, so the same reward cannot be recorded twice.
- A client application requests API access. App registration and API key are verified; reward entitlement and anti-fraud routines run before any account is credited.
02Event and workflow triggers
The synchronisation subsystem defines the outbound and inbound event path: webhooks are configured against an event listener network, sync rules define what a received event should move, and a resilience controller governs retry behaviour when a triggered sync fails.
Server-side, event handling runs in Firebase Cloud Functions rather than in the web app, because XOM builds as a static export. Two functions carry the recurring event load: one processes posts and their triggers, one dispatches push and email notifications.
Within gameplay, the quest engine includes a dedicated conditional-triggers module for event-based quest activation, alongside a core state machine, dialogue, rewards, waypoints and a database sync module for persistent quest state.
03Content tagging
Tagging in XOM is largely automatic. The content intelligence subsystem in the AI layer is specified to perform automatic content categorisation, tagging and quality scoring. Tagged content is then distributed across thirty-four industry verticals, which is what allows the feed algorithms to filter by interest domain.
Advertising uses a parallel and explicitly authored tag set: each ad creative carries a targeting block of user types, interests and geographies, and the ad engine filters against a user profile at serve time.