CEM

Core Traits

CEM sees a game less as a solo experience and more as "things that happen between people". They believe system fun is amplified by community, and design structures that make players aware of each other (parties, roles, trading, UGC, social goals, memes).
For CEM, the core isn't just DAU; it's relationships and trust that give players a reason to stay. In short, CEM is strong at activating the playground and scaling it into culture through participation and relationships.

CEM leans on motivation psychology: in Self-Determination Theory, relatedness is a core need. Structures that let people start together, solve together, and brag together turn play into a social promise, and that promise becomes retention and culture.
So CEM asks with every feature: does it strengthen relationships, or does it erode trust?

In practice, CEM often thinks about norms before features. The same chat or matchmaking can become warm or toxic depending on policies, reward structures, and communication design.
CEM wants growth but manages the "trust line": they know short-term stimulation can destroy the community long-term, so they treat safety and quality as part of the product.

Core Values

Team Chemistry

• When working with Community Producer (CEM), it's important not to separate feature design from operating policy. 'A feature shipped without operations' almost always turns into an incident.
• With Meta Gardener (SEM), long-term live-ops chemistry is strong. When Community Producer (CEM) structures participation signals, Meta Gardener (SEM) can cultivate them into a healthy meta and ecosystem.
• With Rule Conductor (SDT)/Data Pilot (SET), trust lines strengthen. Rule Conductor (SDT) sets fairness baselines and Data Pilot (SET) detects anomalies early, reducing the blast radius of community issues.