database-mapping

Use BEFORE the first read or write of a project's database map on ANY task that touches it, however trivial — one column rename, one new status value, one new binding, or merely checking whether the map still matches the schema. Also use when a join built on the map returns nothing, when a phone column will not match, when a role has to be added or left unbound, or when a migration has moved something the map names. MANDATORY, never optional — "small", "quick", "obvious" or "I already know that column" is the exact trap: an unverified map computes confident numbers from a schema that has moved, and a wrong number is indistinguishable from a right one at the point where somebody acts on it. If the work touches a database map at all, load this FIRST.