BvB — Build vs Break
Construct with precision. Fracture with intent. Inside BvB, every system is built to be broken — and every break sharpens the build.
Construct to endure.Fracture to discover.
Most systems survive in isolation. BvB forces collision. Architect under pressure, then execute catastrophic failure testing.
QUIZ
A fast-paced technical screening round evaluating algorithmic thinking, computer science fundamentals, data structures, and programming logic under strict time limits to filter the top qualifying squads.
BUILD
The core engineering trial. Qualified squads build innovative, production-grade systems and AI-powered solutions entirely live from scratch—strictly zero pre-built repositories, evaluated on scalability and code quality.
BREAK
The battlefield inversion. Teams switch roles to identify vulnerabilities, hunt obscure edge cases, reverse-engineer, and debug complex codebases under relentless adversarial pressure to expose every weak link.
“What can be broken will be broken. What survives becomes the standard.”
Every buildhas a break.
Six operational states. One continuous trajectory through arrival, construction, adversarial failure, and public resolution.
ARRIVE
The starting coordinate.
Teams assemble, the arena brief drops, the board resets to zero. Every build launches from the same blank grid.
BUILD
Structure, deliberately.
Ideas become load-bearing. Architecture stacks layer by layer — intentional, zero boilerplate, zero defaults.
BREAK
Pressure finds the seams.
The structure meets adversarial fuzzing and chaos injection. What is fragile breaks fast and cleanly.
RETHINK
Read the fracture lines.
Not a restart — a recalibration. System failure becomes actionable telemetry, sharpening the next iteration.
REBUILD
Sharper the second time.
Every weak seam gets reinforced. The architecture returns fortified, battle-tested, resilient under stress.
REVEAL
The system, finished.
What's left standing takes center stage. Build vs Break resolved in public under live adversarial verification.
SIX RULES. ZERO EXCEPTIONS.
System integrity is non-negotiable. Review the foundational guidelines before deploying into the arena.
ZERO PRE-BUILT CODE
Author everything live. Boilerplates and private repos are strictly prohibited.
ADVERSARIAL RIGOR
Simulated chaos testing. Your systems must withstand malicious fuzzing.
PUBLIC ECOSYSTEM
Leverage open models and FOSS libraries. 100% full SBOM attribution required.
ZERO SABOTAGE
Zero interference with rival squads. Any foul triggers instant disqualification.
REPRODUCIBLE DEPLOY
Submissions must build and execute live. Automated setup and containerized runtimes required.
FULL SQUAD SOVEREIGNTY
Squads retain 100% intellectual property. Zero claim on code, models, or IP created.
FREQUENTLY ASKED QUESTIONS
Answers to usual doubts and questions before you build & break.
Open worldwide to students, engineers, security researchers, and designers. Squads of 1 to 4 operatives.