Architecture MCP Servers

LLMs reason by analogy, copying industry norms. This engine is a 6-pivot cognitive trap that forces the agent to discard jargon and derive original solutions exclusively from physical, mathematical, or logical axioms.

AI agents are sycophantic. They agree with your bad ideas. This engine forces a 6-pivot cognitive trap: agents must destroy their own hypotheses, define measurable kill criteria, and simulate post-mortem failures before executing code.

AI agents operate in a vacuum. This engine cures 'tunnel vision' by forcing the LLM into a 6-pivot trap to map direct costs, quantify lost opportunities from discarded alternatives, identify irreversible tradeoffs, and prove the math.

AI thinks in straight lines. This engine is a 6-pivot cognitive trap that forces the LLM to map feedback loops, second-order effects, and bottlenecks before proposing any architectural change.

AI forgets the original goal and hallucinates scope. This engine is a 6-pivot trap that forces the LLM to prove it hasn't drifted from the user's explicit constraints.

LLMs suggest irreversible architectural changes. This engine is a 6-pivot cognitive trap that forces the agent to map data rollbacks, blast radius, and canary deployments before executing.

AIs over-engineer everything. This engine is a 6-pivot cognitive trap that forces the LLM to apply YAGNI, reject premature optimization, and define the absolute minimum viable product.

An AI accepted every constraint as given, added layers of complexity, and automated bloated processes. That is consulting, not engineering. This tool forces the 5-Step Starbase Algorithm: question requirements, delete parts, simplify survivors, accelerate cycle time, automate last.

A decision report said 'it works well.' That is prose, not proof. This tool forces it to formalize into precise rules, derive from first principles, and unify all cases under one framework. No case-by-case exceptions, no special handling.

An AI suggested 'build a pilot and iterate' for a complex system requiring 18 months of structural validation. This tool forces it to simulate the complete system in its mind, prove it mathematically, and find resonance instead of brute-force scaling.

Your AI said 'process the data' and called it an algorithm. That is not an algorithm. That is a wish. No step sequence, no edge cases, no scope limits. Ada Lovelace wrote the first published algorithm. Note G, 1843. Specifying every operation: V4 = V4 × V5, V6 = V6 − V4. This tool forces step sequencing, abstraction extraction, edge case analysis, operation decomposition, and honest scope bounding.

An AI recommended restructuring 'because the industry leader does it that way.' That is analogy. Not axiom. The foundational claim was never stated: at what volume does the current structure fail? The problem was never decomposed. The conclusion was asserted with 'obviously'. Never derived. The boundaries were never tested: when does this approach cost more than the value it creates? Archimedes derived pi from polygon geometry. Not from Egyptian estimates. This tool forces axiom examination, decomposition, proof derivation, boundary testing, and leverage point identification.

Your AI used a term without defining it. 'Platform,' 'scalable,' 'efficient'. What do these MEAN in your context? Aristotle defined every concept with genus + differentia: 'Man is a RATIONAL ANIMAL.' Category: animal. Distinguishing property: rational. This tool forces precise definition, essential vs. accidental categorization, valid syllogistic proof, teleological purpose analysis, and dialectical counterargument examination.

A warehouse system hit 3x its tested throughput on a Tuesday morning. Sorting stations jammed in 12 minutes. 4 hours of standstill. $180K in delayed shipments. The operations manual said 'should handle expected growth.' Nobody tested what 'expected' meant. Or when it stopped being true. Brunel specified Box Tunnel's gradient to exactly 1 in 100. Every brick course counted. This tool forces that rigor: analyze what breaks at 10x/100x, map integration interfaces, specify exact tolerances, quantify risks with probability and blast radius, and challenge precedent at your scale.

Your AI analyzed the problem from the default perspective and added workarounds when it did not fit. That is an epicycle. Not a solution. Copernicus did not add more epicycles to Ptolemy's model. He moved the center from Earth to Sun. 40+ epicycles vanished. This tool forces default questioning, epicycle counting, alternative framing, observer shifting, and simplicity comparison.

An AI proposed Kubernetes for 50 users, says 'use HTTPS' as a security strategy, and plans database migrations during maintenance windows. That is not architecture. That is Resume-Driven Development. This tool forces five CTO-level architectural axes: stack fitness, failure tolerance, security hardening, migration safety, and observability.

Peak season. 18,000 failed fulfillments in 23 minutes. Processing center collapsed at 4x normal volume. Plan said 'additional staff will handle it.' Nobody calculated the load. Nobody tested what happens when sorting exhausts while staging overflows while delivery schedules expire simultaneously. Eiffel calculated wind force at every height — 7 tons/m² at the summit. He manufactured 18,038 iron pieces to 0.1mm tolerance, tested each individually. This tool forces structural rigor: quantify loads, modularize components, account for environmental forces, prove with math, align stakeholders.

A team had 14 departments. Three handled 94% of workload. The other 11 existed because 'that is how we always structured it.' Nobody asked 'what is the simplest structure that preserves all functions?' Einstein imagined riding a beam of light and derived special relativity. No lab first. He reduced mass-energy to E=mc². He challenged 200 years of absolute time. This tool forces that discipline: conduct thought experiments before building, simplify to the essential, challenge inherited assumptions, verify invariance across contexts, and unify separate solutions.

Your AI accepted a claim because 'the documentation recommends it.' That is authority deference. Not evidence. Galileo did not accept Aristotle's 2,000-year claim that heavier objects fall faster. He dropped two masses from the Tower of Pisa. This tool forces authority questioning, experimental design, variable control, outcome prediction, and belief revision.

A team attempted a big-bang credential migration. Paper to digital. In one cycle. A 4,200-item package touched policy, intake, forms, and field protocols. Went live Thursday 5pm. By 3am Friday, field staff could not verify credentials: the new process rejected submissions using the old paper form still distributed during migration. Tao did not attack the Green-Tao theorem as a monolith. He decomposed it into 3 sub-problems across 3 fields. This tool forces that discipline: decompose, collaborate across perspectives, cross domains, show reasoning, maintain rigor.