Built to measure GPT-6 Astra. Not measured yet.

I will say the awkward part first. Replay can read what GPT-6 Astra writes, and it knows Astra's published pricing, but I have never measured a real Astra session. So I do not have an Astra number, and I am not going to produce one.

What exists in the shipped build: the reader for the rollout format Astra writes, and the pricing rules that go with it. The path is there and the code runs.

What does not exist: any actual Astra traffic of mine to run it against. Generating enough of it to measure costs money I do not have right now.

So where an Astra figure would go, Replay prints NOT MEASURED. That is not a placeholder I forgot to fill in. It is the honest state of the evidence, and I would rather ship it that way than guess a number and watch someone repeat it as though somebody had checked.

What I am trying to do is get the resources to run real Astra workloads, then publish what comes back with the date it was read and the build that read it, the same way every other figure in this project is published. Until that happens the field stays blank, and it should.

If you are running Astra and you have rollouts sitting on disk, that is the fastest way this stops being a blank. I would like to hear from you. And if the reader gets your logs wrong, I especially want to know, because a reader nobody has tested against real traffic is a claim rather than a result.

go install github.com/RedRobotKK/Replay/cmd/replay@latest

It reads local files and sends nothing anywhere.