Paul Dix

I wanted a couple of very light touch points where it could integrate.

And then I wanted all the net new code that it's creating

to be basically like a new crate within the Rust project.

And I gave it this guidance.

I said, use the Go implementation as your gold standard.

Two things you have to do.

One, get to the point where you can run this test suite as soon as possible and make the simplest test pass.

So do that, write the scaffolding and use the Go implementation as both the guide for how to do it.

So the structure should be roughly the same, obviously taking language idioms into account and do that and then basically just like crank on that.

And it cranked in the background on that.

And that test suite, by the way, is like, it's like 1100 tests.

It's very, very extensive.

It covers all of the functionality of PromQL.

And I just had a crank on the background.

And meanwhile, I have other development work that is my primary development work.

And then all the other, you know, founder-y, executive-y kind of stuff.

and it got really really far but it couldn't quite finish it and then codex gpd5 and codex came out and at that point opus 4-1 is kind of like stuck and spinning its wheels and again like this was all just vibe coded stuff like i gave it the the parameters but i wasn't paying attention to the code it wrote because i was like this is all just like a ridiculous kind of like test and then codex came out and i had to pick it up and it was able to take it the rest of the way

And basically what it created is, like I said, a native Rust implementation of PromQL that's inside the InflexDB 3 code base where InflexDB, you can set it up and it will act like a Prometheus server in terms of the remote write APIs there and all the query APIs are there for getting labels and executing queries and stuff like that.

And it got to the point where it passed the test suite.

Now, the test suite doesn't actually test the Prometheus HTTP API.