The catalogue of traps

A quick-reference index, not a re-telling. Each trap below is the one-line form of a principle from the laws (Part 1) or a chapter, so when you get bitten you scan this list, then go read the full law behind it. Keep your own version, add to it as you get bitten, and let each entry carry its incident (Law 1).

• "Not pushed" is "gone." Unpushed local work vanishes on a re-clone. Push after every unit.
• Wrong account, "repository not found." A failed push is often the wrong identity active, not a real error.
• The green check that never ran. A test suite wired to run nowhere passes by doing nothing. Make it go red on purpose first.
• The verification written but not executed. Worse than none: it closes the subject. Ship the command and the regression signal, not the reassurance.
• Deploy did nothing? Clear the cache. The most common "my deploy didn't take" is a stale cache.
• Code shipped, schema didn't. A deploy carries code, not your migration. Order and backward compatibility matter.
• The name that lies. An object named one thing means another; a relationship built on name resemblance rejects most of the rows. Prove with usage, not names.
• Money as a decimal. Rounding invents and loses money. Store cents as whole numbers.
• The replayed webhook. The same event arrives twice. Without a uniqueness guard, you double the effect.
• The full-access key in the frontend. One leaked powerful key opens the whole database. Server-side only, always.
• Two agents, one file. Parallel work on the same big files collides. One wave at a time per area.
• The doc you trust that's a hypothesis. Your own doc is dated and unverified until proven against the real thing.