Methodology presented by Martin Gamsjaeger in which a team agrees on a set of axioms — sentences everyone accepts as universally true — and then derives assumptions and concrete process constraints from them using informal logical reasoning. The goal is to eliminate discussion about simple things so that, when facing a decision, team members reliably reach the same answer. Core axioms identified by the team include: clients hate bugs; clients love progress; redundancy provides no value (the master axiom); inconsistency provides no value; human attention varies over time; automation reduces the need for human attention; required semantics change over time; tools aren't perfect but we can imagine a perfect one. Assumptions derived: a well-defined process increases team performance; automated checks are preferred over reviews; push constraints as deep as possible; reject invalid input as early as possible; never self-censor on reviews. Builds on the concept of commit-level Transformations with enforced priority and atomicity.