The Four-Part Pattern

Most durable mechanics use four parts. First, a definition file explains the reusable thing: a Language, Divine Power, Class, Species, Weapon, Armor, Tool, Food & Drink record, Condition, or other catalog entry. Second, a small row on Character or runtime state records this person's choice or changing relationship to it. Third, one canonical Rule explains how play interprets that state. Fourth, a concise GM Instruction tells the Game Master when to load and apply the rule.

This separation prevents duplication. A Language owns its script and dialects; Species and Class records own inherited defaults; each Character owns learned Languages and personal overrides; the computed effective list combines them for play. A Divine Power owns personality and communication style; each Character owns faith tier and standing. Each specialized item owns its reusable rules; each Character owns quantity, equipped state, attunement, and personal notes.

Before adding a field, ask: is this reusable definition, irreproducible personal state, a deterministic result, or presentation? Put shared facts on the definition. Keep choices and mutable facts in state. Compute reproducible values. Put labels and visual grouping in layouts. One fact should have one authoritative home.