AnalysisPost-adjudication
Count reconciliation
Every count noun defined and reconciled: 5,505 runs ≠ 4,916 replay contract ≠ 36,251 requests ≠ 30,530 ledger calls.
| Quantity | Count | Definition |
|---|---|---|
| Distinct run IDs | 5,540 | any event in the store |
| Archived completed runs | 5,505 | runs with run.completed, all phases |
| Confirmatory replay contract | 4,916 | 320 P3/X1 + 20 baselines + 2,864 P4 + 1,712 P5 |
| Capsule total | 4,919 | 4,916 confirmatory + 3 legacy diagnostics |
| Round events | 54,276 | simultaneous move pairs |
| Seat-round decisions | 108,552 | two per round event |
| Provider-request events | 36,251 | all llm.requested, full store |
| Phase 4–5 ledger calls | 30,530 | transactional budget ledger (13.1M in / 45.2k out tokens) |
The ~1.5 output-token average per call is expected: valid actions were ordinarily one-token completions even though max_tokens=16. The reconciliation exists because an early draft conflated two of these scopes — a Round 2 queue item.