SPEC → IMPLEMENT → VERIFY → FUZZ → SHIP
One run of the pipeline that produced TrinoX. Each stage emits the typed artifacts described in the system-design doc; counterexamples loop back as planner tickets. Click any stage after the run completes to inspect its artifacts and logs.
What you just saw
SPEC
Machine-readable extraction of Trino behavior: grammar in BNF, function catalog, REST schemas, SPI traits. Reduces "build a Trino-compat engine" to "satisfy this typed spec."
Multi-agent build & verify
Planner decomposes scope into a ticket DAG. Coders fan out. Cross-provider reviewer pool critiques. Property tests, differential tests, and AlphaVerus-class proofs run before merge.
Continuous fuzz, then ship
SQLancer + sqlsmith generate millions of queries diffed against the upstream binary. Antithesis-class DST injects faults under a deterministic scheduler. Jepsen gates every RC.