How shriya-sai/flybreak works
FlyBreak is a browser-based neural-network strategy game: players inspect a live route from LC4 to DNg108, intervene with cuts or jams, and try to contain the signal while preserving protected outputs. The README identifies the shared graph engine, derived MaleCNS level data, replay, and computed bot comparisons as product capabilities. Source excerpts do not include the browser implementation, so the game-level breakdown and links rely on README statements rather than inspected internals.
Main entry points: graph-engine.js Graph Engine · game.js Game Interface · malecns_lc4_dng108.json Curated Level Data
Components 11
Live Gameplay
- Game Interface
dist/game.js - Cut & Jam
dist/game.js - Live Rerouting
dist/game.js - Containment & Collateral
dist/game.js
Graph Rules
- Graph Engine
dist/graph-engine.js - Path & Capacity Rules
dist/graph-engine.js
Replay & Comparisons
- Intervention Replay
dist/game.js - Bot Baselines
dist/game.js
Connectome Level
- Curated Level Data
data/derived/malecns_lc4_dng108.json
Other components
- Player
- MaleCNS Dataset
Connections 10
- Player → Game Interface: plays
README.md - Game Interface → Curated Level Data: loads
README.md - Game Interface → Graph Engine: uses
README.md - Cut & Jam → Graph Engine: apply rules
README.md - Live Rerouting → Graph Engine: recompute routes
README.md - Containment & Collateral → Graph Engine: compute metrics
README.md - Graph Engine → Path & Capacity Rules: enumerates paths
README.md - Intervention Replay → Graph Engine: replays with
README.md - Bot Baselines → Graph Engine: compares with
README.md - MaleCNS Dataset → Curated Level Data: derived from
README.md