●imit8 · liveverdicts · trajectories · provenance

/03 imit8 forensics

Not tokens and latency.
What your pipeline did, and why.

Verdicts as first-class events. Retries as groups. Monotonic-progress trajectories. Artifact-chain provenance. Standalone, or paired with the Studio.

Built on four ideas your APM tool didn't think it needed.

Token counters and latency histograms tell you nothing about whether your pipeline succeeded. imit8 starts from the verdict and works backward.

  1. /01

    Verdicts, first-class.

    Every step emits a verdict: pass, warn, fail, retry, abort. Filter by verdict. Aggregate by verdict. Build dashboards on verdict, not on token counts.

  2. /02

    Retries as groups.

    Three tries of the same step aren't three separate rows. They're one retry group with a trajectory. You see whether the run is converging — or spinning.

  3. /03

    Monotonic-progress.

    Same-state retries don't just look wasteful — the circuit breaker treats them as such. 4/6 → 5/6 → 5/6 is an abort signal, not a recoverable hiccup.

  4. /04

    Provenance is a chain.

    Click any verdict. Walk back through the artifacts that produced it: agent, prompt, model, retry id, scorer trajectory. No more guessing which prompt did the damage.