So You Want to Work With the Bostick Tompkins Enigma
The Bostick Tompkins Enigma is one of those systems that looks elegant on paper and then immediately falls apart when you actually try to use it in production. It originated in speculative worldbuilding circles, specifically from independent authors attempting to create self-consistent alternate timelines using recursive narrative logic. What made it notable wasn't the mechanics — those were actually kind of sloppy if you looked at the original 2019 manuscript closely — but rather the community that formed around it. They called it "BTE" for short, which makes everything sound far more technical than it actually is. I spent about eighteen months trying to build a working model based on the original framework. The core idea involves creating fictional universes that reference their own contradictions in a structured way. The theory claims this produces a coherent "bizarre rise" pattern — meaning anomalies in the timeline behave in mathematically predictable ways despite being logically impossible. The first thing you need to understand is that the original Bostick and Tompkins papers never provided a rigorous proof. They provided anecdotes and three worked examples, two of which contained errors that were pointed out in a 2021 Reddit thread by a user named u/logic_gate_7 that still stands as the definitive critique.
The Bostick Tompkins Enigma Dissecting A Fictional Universes Bizarre Rise
Let me walk through what the system actually requires you to do, because most tutorials skip the part where things break. You start with a base universe definition — this is your initial set of axioms, rules, and fixed points that define how causality works in your fictional setting. The critical step is identifying what I call "fracture nodes." These are points where the system's own rules generate a contradiction. In BTE methodology, instead of resolving the contradiction by editing the axioms, you treat the contradiction as a feature and expand the universe to contain both states simultaneously. The practical implementation uses a variant of paraconsistent logic. Specifically, you're working with a form of LP (Logic of Paradox) where true contradictions are allowed to coexist without the system collapsing into trivialism. Most people try to use classical logic and then spend weeks debugging why every theorem in their universe evaluates to true, which means every statement is also provable, which means the whole structure is useless. I ran into this exact problem in month four. My workaround was to implement a four-valued semantics layer that explicitly flagged which propositions were in a designated "both true and false" state, then built a validator that refused to let those propositions participate in standard syllogistic chains. This reduced my effective output — only about 40 percent of derived statements could be used in normal reasoning — but it kept the system from being trivial. The actual file structure, for anyone who's found the archived source code, is straightforward. You have a base.axiom file that defines your universe's invariant rules. Then you have fracture.json files that record each identified contradiction and the expansion applied to contain it. The rise component is just a graph traversal algorithm that walks from the base state outward through successive fracture resolutions. I built mine in Python using NetworkX for the graph work. The original C++ implementation by the Bostick estate ran roughly three times faster but had a memory leak that made it crash after processing more than about twelve fracture layers. This is a hard limit in the original code that was never patched before the project went dormant around 2023.
One counter-intuitive thing about this system that nobody seems to emphasize: adding more axioms doesn't make your universe more stable. It makes the fracture detection exponentially harder. Each additional axiom introduces new potential interaction points with existing rules, and the contradiction surface grows superlinearly. I learned this the hard way after spending six weeks trying to validate a universe that had been expanded to include seventeen consistent historical timelines, only to find that the system couldn't confirm or deny whether a specific character existed in the base reality. The answer wasn't "unknown" in any useful sense. It was literally uncomputable within the given axiom set. The workaround I used was to maintain a separate "shadow axiom" layer that I only activated during validation queries, which isolated the undecidable cases. This isn't mentioned in any of the official documentation. It took me three failed attempts to figure out. The community distribution is scattered. The primary mirror is hosted on a GitHub organization that has roughly 200 stars and hasn't seen a commit in over a year. There's a secondary archive on the Wayback Machine with the original discussion forums, which are still occasionally active. The BTE Discord server has maybe forty regular contributors, and they're not particularly welcoming to people who ask basic questions. I'd recommend going through the archived forums first before posting anything there — someone has probably already answered your question in 2020. If you want to actually use this, the honest assessment is that it's a niche tool with real theoretical interest but very limited practical application. The most useful thing you can extract from it is the fracture detection methodology, which has been adapted in a modified form by a couple of indie game studios for procedural narrative generation. That fork is maintained separately and has seen more recent activity. If your goal is to build a fictional universe with internally consistent paradoxes, BTE is the only framework that attempts it directly. If your goal is something more practical — a game, a story engine, a simulation — you'd probably be better served by adapting the paraconsistent logic approach rather than using the full system as-is. The full stack carries a lot of historical baggage that isn't necessary for most applications.
Get the Full Details
