◉ Data IntegrityAxiomSet Theory — Membership, Boundaries, and BelongingEvery input validation bug is a set membership violationTimeless · MathematicsAXM-001
◈ Complexity & PerformanceAxiomBoolean & Propositional Logic — True, False, and the Excluded MiddleEvery conditional branch is a proposition. Every bug is a proof that the proposition was wrong.Timeless · MathematicsAXM-002
◑ Observability & OpsAxiomBayesian Probability — Belief, Evidence, and Updating What You Think You KnowYour test suite passed. How confident should you actually be?Timeless · MathematicsAXM-003
◎ Auth & AccessAxiomGame Theory — Adversaries, Incentives, and EquilibriaSQL injection is a game. The developer chose a strategy. The attacker chose a better one.Timeless · MathematicsAXM-004
◈ Complexity & PerformanceAxiomComputability & Complexity — What Machines Can and Cannot DoSome bugs cannot be detected. This is not a limitation of your tools. It's a theorem.Timeless · MathematicsAXM-005
⬢ Architecture & DesignAxiomGraph Theory — Networks, Dependencies, and PathsEvery dependency tree is a directed acyclic graph. Until it isn't.Timeless · MathematicsAXM-006
◉ Data IntegrityAxiomInformation Theory — Encoding, Entropy, and the Limits of CommunicationEvery encoding bug is a violation of Shannon's channel capacity theoremTimeless · MathematicsAXM-007
◎ Auth & AccessAxiomNumber Theory & Cryptography — Primes, Modular Arithmetic, and the Foundations of TrustEvery HTTPS connection you've ever made depends on a theorem from 1640Timeless · MathematicsAXM-008
⬢ Architecture & DesignAxiomFormal Logic & Type Theory — Proofs as Programs, Types as TheoremsThe Curry-Howard correspondence says every type annotation is a mathematical proof. Every type error is a theorem violation.Timeless · MathematicsAXM-009
◆ Injection & InputCode FlawThe Concatenated QueryWhen the boundary between code and data dissolvedLate 1990s · PHP 3/4EXP-001
◈ Complexity & PerformanceCode FlawThe Greedy InitializerConfusing 'application ready' with 'application loaded everything'Early 1990s · Visual Basic 3 / VB6EXP-002
◑ Observability & OpsDesign FlawThe Ouroboros Health CheckWhen the observer became the observed's worst enemy2010s · Go / Node.jsEXP-003
◎ Auth & AccessDesign FlawThe Phantom SessionWhen identity lived in a cookie anyone could guess2000s · PHP 4/5EXP-004
◉ Data IntegrityCode FlawThe Trusting DeserializerWhen the application ate whatever it was fed2010s · Java 6/7EXP-005
⬢ Architecture & DesignDesign FlawThe God ObjectOne class to rule them all, one class to bind them1980s · C++ / DelphiEXP-006
◉ Data IntegrityCode FlawThe Unquoted CSVWhen commas destroyed the boundary between fieldsEarly 1990s · Visual Basic / PerlEXP-007
◇ Design AssumptionsRequirement FlawThe Runaway MigrationIt worked in dev. It locked prod for four hours.2000s · SQL / RailsEXP-008
◈ AI-Assisted EraDesign FlawThe Autonomous ExecutorWhen the AI did exactly what you said, and that was the problem2020s–Now · Python / TypeScriptEXP-009
⬡ Memory & SystemsCode FlawThe Unsynchronized HandshakeWhen two threads reached for the same thing at the same timeLate 1990s · Java 1.2 / C++EXP-010
◈ Complexity & PerformanceCode FlawThe Dead BranchCode that compiled, deployed, and never once executedEarly 1990s · C / Visual BasicEXP-011
⬡ Memory & SystemsCode FlawThe Overflowed ReturnWhen the input kept writing past the end of the room1970s · CEXP-012
◆ Injection & InputCode FlawThe Embedded ScriptWhen user input became someone else's browser codeLate 1990s · JavaScript / PHPEXP-013
◎ Auth & AccessDesign FlawThe Forged RequestWhen your browser attacked you while you were logged in2000s · HTML / PHPEXP-014
◎ Auth & AccessDesign FlawThe Open DoorWhen the only thing protecting your data was a number in the URL2000s · PHP / JavaEXP-015
◎ Auth & AccessCode FlawThe Committed SecretWhen the password was in the source code the whole time2010s · Python / JavaScriptEXP-016
◉ Data IntegrityDesign FlawThe Poisoned DependencyWhen npm install ran someone else's code before yours2010s · JavaScript / PythonEXP-017
◆ Injection & InputDesign FlawThe Instructed HallucinationWhen the model couldn't tell the user's data from the user's instructions2020s–Now · Python / TypeScriptEXP-018
◉ Data IntegrityDesign FlawThe Hardwired YearWhen two digits seemed like enough for forever1940s–50s · COBOL / Punch CardEXP-019
◈ Complexity & PerformanceCode FlawThe Tangled GotoWhen control flow became a maze with no map1960s · FORTRAN / COBOLEXP-020
⬡ Memory & SystemsDesign FlawThe Unguarded MemoryWhen every program could read and write everything1960s · Assembly / FORTRANEXP-021
◈ Complexity & PerformanceDesign FlawENIAC — The First Programmers Debugged with Their HandsWhen there was no line between hardware and software1940s–50s · Physical WiringEXP-022
◉ Data IntegrityDesign FlawThe Dropped Deck — Why Code Has Line NumbersWhen sequence was stored in the physical arrangement of atoms1940s–50s · Punch CardEXP-023
◈ Complexity & PerformanceDesign FlawSAGE — The First Software CrisisWhen 250,000 lines consumed half of all programmers in America1940s–50s · AssemblyEXP-024
◉ Data IntegrityDesign FlawLEO I — The First Business Computer BugWhen automation amplified errors as effectively as efficiency1940s–50s · Machine CodeEXP-025
⬢ Architecture & DesignDesign FlawApollo Guidance Computer — The Software That Saved the Moon LandingWhen error recovery by design prevented catastrophe in real time1960s · AGC AssemblyEXP-026
◉ Data IntegrityDesign FlawThe Precomputed JudgmentWhen the senior move is to change the shape of the data, not write a longer queryEarly 1990s · SQLEXP-027
◉ Data IntegrityDesign FlawThe Hand-Cut PartitionWhen the license was too expensive so you built the infrastructure yourselfEarly 1990s · SQLEXP-028