How content is structured
Your dimension’s content is organised by domain, then subtopic, then tier — every question and campaign decision is tagged to one of these.
Domains and subtopics
Section titled “Domains and subtopics”The platform ships 10 built-in domains (QA, Backend, UI/UX, Platform, AI/ML, Security, Product, Architecture, Data Engineering, Mobile), each with its own set of subtopics and its own unit class and abilities. Your dimension can also define its own domains and subtopics on top of these (Add domains and subtopics). Today only questions can use them: decisions, pools, acts, missions and AI generation accept platform domains and subtopics only. Units, abilities and maps have no domain field at all.
A subtopic always belongs to exactly one domain. A question, decision or incident gate names a subtopic, and the subtopic has to be valid for the domain it’s paired with — pairing a subtopic from one domain with a different domain is rejected.
Every question sits at Tier 1, 2 or 3 — see Questions and tiers for what each tier tests. A match asks questions in the domain of the hex being moved onto or attacked, at a tier set by that hex’s elevation. A mission’s questions setting names a domain, a tier range and (optionally) a list of target subtopics within it; a match asks questions in that domain, within the tier range, weighted toward the target subtopics (and toward the ones the player is weakest at).
Your content plus the platform’s
Section titled “Your content plus the platform’s”Your dimension’s own authored content (questions, units, abilities, maps, acts, missions, decisions, pools and decision effects) sits alongside the platform’s own content, not instead of it — unless you’ve switched content mode to org-only content under Mix platform and your own content. Anything you author uses the same domain/subtopic taxonomy as the platform content around it, whether that’s a platform domain or one you defined yourself.