SDM

Core Traits

SDM sees a game less as content that delivers a right answer, and more as a rule engine that multiplies possibilities. They rate the best moments as the ones where systems interlock and unexpected outcomes burst out, not where players follow a scripted path.
So SDM designs around combinations and interactions: one system calls another, a new layer sits on top, and the strategy space expands. In short, SDM prefers sturdy rules, but wants results to explode through player combination and invention.

From an MDA (Mechanics-Dynamics-Aesthetics) lens, SDM treats Dynamics as the primary design target. Mechanics are not a device for delivering a "right answer" but a reaction system where player actions collide and create new situations; as those dynamics repeat, the strategy space expands.
SDM's fun model is that interactions keep generating new problems even without adding new content.

In practice, SDM cares most about whether players can set their own goals. Even with limited content, if the system reproduces new situations, replay stays alive and the community creates its own play culture.
If guardrails are weak, abuse and collapse arrive fast. SDM loves emergence, but they don't ignore live-ops cost or onboarding friction; they obsess over finding the threshold where a deeper rule design is still worth paying for.

Core Values

Team Chemistry

• When working with System Alchemist (SDM), first agree what emergence is allowed and what abuse must be blocked. Without that line, discussion expands endlessly.
• With Data Pilot (SET), you can become the best partners: Data Pilot (SET) quickly finds collapse points via observation/experiments, and System Alchemist (SDM) redesigns rule connections to stabilize things long-term.
• With Rule Conductor (SDT), there may be early friction, but once Rule Conductor (SDT)'s baseline (judgments/exceptions) becomes System Alchemist (SDM)'s guardrail, combinatorial systems become much safer.