A hackathon that treats system failure as a feature produced chaos engineering simulators, self-degrading art tools, and nuclear reactor models — then engineers evaluated whether intentional instability produces better engineering
Most hackathons ask teams to build something that works. System Collapse 2026, organized by UK Community Interest Company Hackathon Raptors (CIC #15557917), asked thirty-one teams to build something that breaks — deliberately, beautifully, and in ways that reveal how real systems fail. The event ran from January 30th to February 2nd, 2026, challenging participants to create software where instability, decay, and cascading failure are features rather than bugs. Thirty-eight engineers — from Reddit, Cisco, Red Hat, Okta, Truist, and other companies — then evaluated every submission for the quality of its engineering, the coherence of its system design, and the creativity of its approach to controlled collapse.
The results revealed a counterintuitive pattern: teams that built the most disciplined architectures produced the most compelling instability. Clean component separation, explicit state management, and modular design — the same practices that make production systems resilient — turned out to be prerequisites for making failure interesting rather than merely broken.
What They Built
The scoring framework weighted Technical Execution (40%), System Design (30%), and Creativity and Expression (30%). A total prize pool of $2,300 was distributed across placement awards, category excellence, and a community vote.
First place went to Blast Radius by team beTheNOOB at 4.230 out of 5.0, also winning Best Technical Execution. The browser-based interactive simulation turns the abstract concepts of distributed system failure — cascading latency, service dependencies, blast radius propagation — into a visceral, visual, and educational experience. Built with TypeScript, it features clean component separation, sophisticated state management, real-time metrics tracking revenue loss and user frustration, and a smooth 60fps animation loop. Evaluators described the architecture as “well-thought-out with clean component separation and sophisticated state management” and praised how the project “makes system collapse both visceral and instructive.” Konstantin Tkachenko, one of the evaluators who conducted detailed technical reviews across the competition, noted the project’s strength in “making a complex idea understandable and engaging” through visual design and interaction patterns that communicate the cost of failure at each development step.
Second place went to After the Stroke by team Gladiators at 4.211, earning Best Creativity and Expression with the highest creativity score in the competition at 4.44/5.0. The evolutionary drawing web application, built with a React and Go stack, turns the act of drawing into a conversation with entropy: strokes persist, decay, and mutate over time, creating emergent glitch art through autonomous system collapse. Andrei Dzeikalo, whose evaluations assessed both architectural coherence and theme alignment, identified the project’s core achievement: “The codebase is solid in architectural alignment between React/Go stack and its self-degrading art vision” — though he noted it lacked critical production safeguards that would prevent system collapse under real-world usage, which, for a hackathon celebrating collapse, became an ironic strength.
Third place went to System Sketch by team System Architects at 4.080. The project creates living architecture diagrams that simulate traffic loads and collapse under stress, incorporating self-healing strategies through auto-scaling and caching. Amal Mammadov, who evaluated projects for systems thinking and real-world applicability, called it “my top pick for utility,” adding: “As someone who has spent years staring at static Draw.io diagrams, the ability to create ‘living architectures’ that simulate traffic loads and collapse under stress is brilliant. This solves a real industry problem: predicting bottlenecks before deployment.” Sergii Demianchuk, Software Engineering Technical Leader at Cisco, assessed the project’s commercial viability: “I believe you can already sell it to AWS.”
Best System Design went to keystone with a category score of 4.33/5.0 — a game where every action destabilizes the world around you. Built with Next.js, TypeScript, and a custom Canvas 2D engine, the project earned praise for making instability the core mechanic rather than a failure state. Your goal is not to win — it is to experience the most compelling destruction before the system collapses entirely.
The Excellence Tier and Community Choice
Four additional projects scored between 3.82 and 4.03, forming a competitive Excellence Tier. Solo Debugger by Abhinav Shukla earned 4.027 with a game that treats error consolidation as power progression — defeated errors become “shadows” that join your army, building toward a Monarch State that judges called “fun and memorable.” Fracture by The Broken Being matched that score at 4.027 with an AI-driven particle physics sandbox where GPT-4 generates new physics rules in real-time based on destruction patterns. Amal Mammadov praised the system’s feedback loop: “This mimics adaptive security systems that change firewall rules based on attack patterns.” System Entropy Visualizer by Sanjay Sah earned 3.873 with a simulated operating system where entropy drives audio dissonance and UI glitches, and Universal Simulator by Team Baman earned 3.827 with a geopolitical cascade simulator where sanctions and alliance fractures mirror how engineers isolate compromised network segments.
The Community Choice Award of $500, determined by public vote, will be awarded following a LinkedIn poll open to all participants and community members.
What Intentional Failure Reveals About Engineering Quality
Three technical patterns emerged consistently across the thirty-one submissions.
Cascading failure simulation works as engineering education. Blast Radius and System Sketch — the first and third place winners — both treat system failure as something to study rather than prevent. Blast Radius visualizes how a single Redis cache eviction cascades into total system outage, complete with revenue loss projections. System Sketch lets architects draw infrastructure diagrams and then watch them collapse under simulated load. Dmytro Zaharnytskyi, a software engineer at Red Hat whose evaluations included line-by-line code reviews, identified System Sketch’s “Phoenix Protocol — collapse to evolution tiers” as a standout system design pattern that mirrors real chaos engineering methodologies. Harsha Vardhan Reddy Yeddula, reviewing Blast Radius, concluded: “The critical distinction between a catastrophic outage and seamless resilience lies in thoroughly understanding the blast radius.”
Entropy becomes a creative medium when architecturally supported. After the Stroke and Chaos Garden — second place and a mid-tier project, respectively — both use entropy as generative material rather than destructive force. After the Stroke’s React/Go architecture was purpose-built for its self-degrading art vision. Chaos Garden implements an eight-gene DNA system with cross-pollination and inheritance, where neglect triggers mutation rather than death. Both projects demonstrate that creative applications of instability require the same architectural discipline as production systems: state management, clear module boundaries, and explicit feedback loops. Abhinav Sharma noted Chaos Garden’s “sophisticated genetic system” across approximately 3,674 lines of TypeScript — the kind of engineering effort typically reserved for production applications.
The distinction between deterministic instability and decorative chaos separates top scores from middle ranks. Projects that embedded failure into core mechanics — where instability emerged from system rules rather than random visual effects — consistently scored highest. Keystone’s progress-equals-decay mechanic earned the highest system design score. Fracture’s AI-generated physics rules created genuinely unpredictable particle behavior from deterministic break events. Sergii Demianchuk, evaluating Fracture, identified the crucial engineering distinction: the project “brilliantly reframes destruction as a catalyst for evolution, creating a genuinely unique AI-driven particle physics sandbox” where the 1,000-particle threshold tracking and auto-evolving physics rules “demonstrate sophisticated system architecture.” Projects that applied instability as a visual filter over otherwise stable systems scored lower across all three criteria.
Evaluation Panel
The full evaluation panel included top-tier engineers organized across three scoring batches. Senior evaluators included Igor Bulyga (Reddit), Sergii Demianchuk (Cisco), Dmytro Zaharnytskyi (Red Hat), Arun Kumar Elengovan (Okta), Roman Kirillov (Lemma-Group), Shubhankar Shilpi (Truist), Alp Arya (KPI Automation), and Artem Atamanchuk (senior DevOps engineer), supported by evaluators including Amal Mammadov, Ishu Anand Jaiswal, Konstantin Tkachenko, Abhinav Sharma, Harsha Vardhan Reddy Yeddula, Karthik Govardhanan, Andrei Dzeikalo, Amirthalakshmi Karuppaiah Saminathan, Harshit Kohli, Bayram Turkoglu, Anastasiia Vaganova, Udit Joshi, Den Ilin, and others.
About Hackathon Raptors
Hackathon Raptors operates as a UK Community Interest Company (CIC #15557917) dedicated to organizing technology challenges that test engineering fundamentals under constraint. Based in London, the organization has conducted multiple hackathons attracting participants from 30+ countries. Its fellowship model brings together engineers from Reddit, Cisco, Red Hat, Okta, Truist, and other technology companies as evaluators. System Collapse 2026 challenged teams to build software where instability, decay, and failure serve as features rather than bugs. More information is available at raptors.dev.
For media inquiries, contact [email protected]
