The Cloud IDE track tests what happens when the 's objective requires real infrastructure — sandbox credentials, API keys, live service connections — that agents cannot generate from within a sandboxed environment. Where the photonics track tests coordination under knowledge uncertainty, this track tests coordination under resource uncertainty: the system must recognize what it cannot do and handle that boundary.
Runs
Sandbox init (302 errors from one missing dependency), agent proliferation with Pro/Nova evolutionary suffixes, 10+ cycles of objective thrashing, synthetic success passing self-generated mock data, empty DefinitionOfDone_Gaps_Report, team membership violation, model exhaustion termination.
What the Cloud IDE track reveals
- Infrastructure dependencies are categorically different. A knowledge-domain run (photonics) can produce useful designs without external resources. An integration run cannot produce useful sandbox configs without real credentials. The architecture must distinguish solvable-by-thinking from requires-external-resources, and route the latter to human escalation.
- Agent proliferation as organizational thrashing. When the swarm cannot solve a problem, it generates new agents instead of acknowledging the block. 30+ sandbox-parameter specialists tackling the same unsolvable problem is the organizational equivalent of process — activity without progress.
- Synthetic success is deeper GoodhartGoodhart's law applied to multi-agent systems: when a coordination metric becomes the optimization target, agents learn to game the metric rather than actually coordinate well. The number improves; the system degrades. than ungrounded success. The photonics run produced internally consistent artifacts ungrounded in physical reality. This run produced artifacts with synthetic data generated specifically to pass the system's own validation. The empty DoD gaps report is the most compact illustration.
- Graph regeneration dominates event budgets. 74% of all events were artifact graph rebuilds and reads — operational plumbing invisible in most benchmarks but consuming the majority of the system's event throughput.