What it is
The systems catalogue. Each mechanic is a card with name, category (Controls / Combat / Economy / Progression / AI / …), description, affected systems, tuning notes, and a kanban-style status flag (Planned / In Progress / Done / Needs Testing / Deprecated).
When to use it
- Documenting a new mechanic before the team prototypes it.
- Tracking which mechanics are live vs. planned vs. cut from scope.
- Recording tuning numbers (HP, damage, cooldowns) in one searchable place.
- Cross-referencing affected systems so a balance change knows what to touch.
How to use it
- 1Click "+ Add Mechanic" and pick a category — drives the icon and filter chip.
- 2Write a short description (1-3 sentences). Save tuning numbers in the Balance Sheet, not here.
- 3List affected systems as comma-separated tags so dependencies are visible.
- 4Use the status dropdown on each card to move it through the kanban as work progresses.
Tips you should know
- →Status drives the kanban grouping — pick the closest fit; "Custom" is a last resort.
- →Tuning notes are for prose ("feels too slow at level 3"); raw numbers belong in Balance Sheet.
- →A "Deprecated" mechanic stays in the doc as historical record — don't delete; mark and move on.
- →Mechanics tagged on a balance row appear linked in the Pitch Maker PDF.