Implement retry/backoff in worker

billing-core · claude-sonnet-4-6 · 120m · 2d ago · Blake Sullivan

Part of: Usage-metering accuracy

Session tokens

731K tokens

731K raw tokens

Avoidable tokens (est.)

88K tokens

12% of session

Quality

craft check score

Outcome

In progress

8 cycles · 1 corrections · 120m wall-clock

PromptGenerateVerifyCorrect

11maccepted

9maccepted

13maccepted

correction

17mrevised

15maccepted

17maccepted

22maccepted

13mrejected

7 verify events · 0 accepts without verify — chips are pinned to the cycles that triggered them.

Grounded answers with mandatory cycle citations

Answers are PROXY — generated over the measured transcript. This query is visible to the engineer in their access log.

What drove the score — pinned to its cycles

Verification discipline98
Every accepted diff was preceded by a verify-type event
Plan-mode discipline73
No plan-mode use in this session
Correction load84
1 of 8 cycles were corrections of earlier output
Prompt clarity98
Context, constraints, and a done-condition raise first-pass acceptance

Clean session — no risk flags.