Add rate limiting to public API

notifications-svc · claude-haiku-4-5 · 28m · 1d ago · Ines Ford

Part of: Bounce-handling fixes

Session tokens

605K tokens

1.8M raw tokens

Avoidable tokens (est.)

73K tokens

12% of session

Quality

craft check score

Outcome

Completed

2 cycles · 0 corrections · 28m wall-clock

PromptGenerateVerifyCorrect

14maccepted

13maccepted

2 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 discipline39
No plan-mode use in this session
Correction load98
No correction loops — the work converged forward
Prompt clarity70
Context, constraints, and a done-condition raise first-pass acceptance

Caught in this session

high
Policy violation
Attempted edit outside allowed workspace path
Flagged in-session by your risk rules