If two layers talk past each other, the player feels gaslit
Systems should reduce doubt, not multiply mysteries. This essay is about the vertical stack: core, metagame, event—each with a legible 'why' for the people who do not read Discord.
A live mobile title often grows like a house with many owners: a neat porch, then a side room, then a balcony that looks lovely until it rains. Each addition is a frame that changes the meaning of the previous room. A currency introduced for catch-up, then reused for cosmetics, then gated behind a new battle pass, is three different stories wearing one icon.
Frame Theory recommends a layer card for each public system: purpose, invariants, and retirement conditions. The retirement field is the adult part. If a team will not name how a system could end, they will, in practice, let it rot until it detonates in a support queue.
Seasonal design can be a gift when it is ephemera with a clean ceiling: players understand festivals as temporary texture. The failure mode is a season that becomes a parallel government with its own courts and vocabulary. Players should not need a private wiki to act as a constitution.
When two systems argue in the data, the player feels the argument in their stomach before your analyst writes the deck. Frame Theory suggests a monthly reconciliation hour where economy, live events, and UX read the same three player quotes out loud. If a quote makes one discipline wince, that is the system boundary you have been avoiding.
Finally, write the player-facing apology before the emergency. If a season must be nerfed, the language should already exist in a style guide: calm, specific, no finger-pointing at players for 'misusing' a system you failed to explain.