Add rate limiting to public API

design-system · claude-haiku-4-5 · 143m · 1d ago · Blake Vidal

Part of: Token theming rollout

Session tokens

522K tokens

1.6M raw tokens

Avoidable tokens (est.)

63K tokens

12% of session

Quality

craft check score

Outcome

Completed

13 cycles · 3 corrections · 143m wall-clock

PromptGenerateVerifyCorrect

15mrejected

10mrevised

11mrejected

17maccepted

5maccepted

accepted w/o verify

7maccepted

accepted w/o verify

10maccepted

correction

6mrevised

12maccepted

#10

14maccepted

#11

10mrejected

correction

#12

14mrejected

correction

#13

11mrevised

9 verify events · 2 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 discipline67
2 of 6 accepts had no verify event between diff and accept
Plan-mode discipline36
No plan-mode use in this session
Correction load70
3 of 13 cycles were corrections of earlier output
Prompt clarity67
Context, constraints, and a done-condition raise first-pass acceptance

Clean session — no risk flags.