BatchZero
A demonstration project for an epidemic investigation agent built on a graph database. It models cases, exposure events, supply chains and evidence as graph nodes, and traces sources through path traversal.
Timeline (last 90 days)
BatchZero is a Graph Hacks 2026 project built for the FalkorDB track, using synthetic data to demonstrate an outbreak investigation workflow; it is not a real public health system.
In BatchZero's synthetic case, two ingredients appeared in all 11 cases and two suppliers tied, so ranking based solely on exposure frequency cannot distinguish them.
BatchZero checks the relationship between exposure dates and case onset times and the pathogen's incubation window, and records falling outside the window are excluded from the valid exposure set.
BatchZero models the workflow as four roles: Intake Officer, Cluster Analyst, Supply Chain Tracer, Briefing Officer, each using a separate MCP server subprocess with its own tool set.
BatchZero records tool calls and sessions in the graph, and evidence links back to the tool call that produced it, forming the path: Hypothesis → Evidence → ToolCall → Session.
When a Groq API key is available, Groq can drive the tool loop; when not, deterministic replay executes the same workflow against FalkorDB.
The project report correctly identified the source in all three benchmark runs.
All Facts (7)
BatchZero is a Graph Hacks 2026 project built for the FalkorDB track, using synthetic data to demonstrate an outbreak investigation workflow; it is not a real public health system.
50%UnverifiedIn BatchZero's synthetic case, two ingredients appeared in all 11 cases and two suppliers tied, so ranking based solely on exposure frequency cannot distinguish them.
50%UnverifiedBatchZero checks the relationship between exposure dates and case onset times and the pathogen's incubation window, and records falling outside the window are excluded from the valid exposure set.
50%UnverifiedBatchZero models the workflow as four roles: Intake Officer, Cluster Analyst, Supply Chain Tracer, Briefing Officer, each using a separate MCP server subprocess with its own tool set.
50%UnverifiedBatchZero records tool calls and sessions in the graph, and evidence links back to the tool call that produced it, forming the path: Hypothesis → Evidence → ToolCall → Session.
50%UnverifiedWhen a Groq API key is available, Groq can drive the tool loop; when not, deterministic replay executes the same workflow against FalkorDB.
50%UnverifiedThe project report correctly identified the source in all three benchmark runs.
50%