Download
Devlog

How Breachworks was made and tested

OneDroid Dark Factory

The pipeline: stages, gates, evidence

  1. docs/dark-factory/01-game-design.md §0

  2. docs/dark-factory/01-game-design.md

  3. docs/dark-factory/02-technical-design.md

  4. docs/dark-factory/03-project-infrastructure.md

  5. docs/dark-factory/04-observability.md

  6. docs/dark-factory/05-qa-vertical-slice.md

Claim labels

  • [C]
  • [I]
  • [A]
  • [O]

Rules first, code second

Kept honest

144
29
6
—
OneDroid Argus

Testing a game from the outside

One full test, fixed in waves

  • 278/311
  • 302/311
  • 310/311
  • 347/347

457
517 → 0.3

Visual QA

How OneDroid Argus learned to see the game

LevelWhere it runsWhat it checksNumbers and proof
L0
L1
L2
L3
L4
48/60
88/96
2906
2078

Fix waves V1–V11

  • V1
  • V2
  • V3
  • V4
  • V5
  • V6
  • V7
  • V8
  • V9
  • V10
  • V11
Recordings

Recordings: making and testing

Releases

From Tunnel Job 0.4 to today

Loading the changelog…

Built with the OneDroid Dark Factory method

Download for Windows Download for macOS Library

Step-by-step install guide

Built with OneDroid

OneDroid Dark FactoryThe method the agents followed: stages, gates, evidence and fix waves. OneDroid ArgusThe tester: markdown scenarios run against the game's own Core, with a judge for every claim.

More from OneDroid: OneDroid Synapse · OneDroid Engram · argus-runner · Docs · Case studies · onedroid.ai