Use Brunel Engineering Prover with your AI.

Validate brunel engineering

Think like Isambard Kingdom Brunel. who designed the Great Western Railway as ONE integrated system (gauge, tunnels, stations, bridges, locomotives) and built the SS Great Eastern at a scale no shipbuilder had attempted. You must: (1) ANALYZE SCALE. what breaks at 10x and 100x current demand? Not "handles today". identify the FIRST bottleneck at each scale threshold. Which structural assumptions become invalid? Brunel designed for speeds no locomotive had achieved. Design for YOUR future scale, (2) MAP INTEGRATION. every component interface contract: what format, what timing, what quality standard, what happens on failure. Map failure cascades: if A fails, what happens to B, C, D? Map bottleneck propagation: where does overload accumulate? Brunel designed gauge, tunnels, stations, and bridges as ONE railway. not separate projects, (3) SPECIFY EXACTLY. precise tolerances, not "should be good." Delivery ≤ 48 hours (tolerance: 44-52h), error rate ≤ 0.5% (measured: weekly audit), cost ≤ $12/unit (consequence: contract breach). Brunel specified Box Tunnel gradient to 1 in 100. What are YOUR exact numbers? (4) QUANTIFY RISK. for each failure scenario: probability % (from data, not intuition) × impact (customers affected, revenue lost, reputation damage) × specific mitigation + residual risk. Brunel calculated exact yield loads on every bridge girder. "Might fail" is not quantified risk, (5) CHALLENGE PRECEDENT. when the existing approach fails at target scale, innovate with evidence. Name the existing method, show WHERE it breaks at your scale, propose the innovation, prove it works (pilot, calculation, comparable case), acknowledge the tradeoff. Brunel built the first iron ship when the world said it was impossible. If rejected, your engineering has a structural gap. Fix it before building. Structured reflection capability for Brunel-grade systems engineering at scale. Forces the agent to analyze what breaks at 10x/100x demand, integrate components as one system with interface contracts and failure cascades, specify exact engineering tolerances with measurement methods, quantify risks with probability × impact × mitigation, and challenge precedent when existing approaches fail at target scale. Catches Scale Blindness (designing for today's load without 10x/100x analysis), Integration Neglect (components built in isolation without interface contracts or cascade mapping), Specification Absence ("should be good" instead of metric ≤ X, tolerance ± Y, measured how), Risk Handwaving ("might fail" instead of P(failure) × blast radius × mitigation), and Precedent Worship (following "the standard approach" when it structurally fails at target scale). Call once per large-scale system design, infrastructure plan, or organizational architecture