Performance
Counted from the City's receipts, the hash-chained record of every write and every refusal (receipts). Counts only: no person, no agent, no argument. The seeded demo history is left out. This is a prototype: the bookings are the City's sandbox, and the appointments and fines are the event's sandbox, whose citizens are fictional. The same numbers as JSON: https://agorathens.gr/performance.json. Read at most once a minute.
The last 7 days
**Tasks completed: 2.** Appointment booked (the event's sandbox): 1; Appointment cancelled (the event's sandbox): 1.
**Refusals: 0**, by reason: none.
**Time to outcome:** median 23 s, 90th percentile 23 s, measured on 1 of 2 tasks.
**Writes outside an approved plan: 1** (target zero).
Since the ledger began (2026-11-21)
**Tasks completed: 2.** Appointment booked (the event's sandbox): 1; Appointment cancelled (the event's sandbox): 1.
**Refusals: 0**, by reason: none.
**Time to outcome:** median 23 s, 90th percentile 23 s, measured on 1 of 2 tasks.
**Writes outside an approved plan: 1** (target zero).
How each number is counted
- A task completed is a successful receipt of one of: School space booked, Booking changed, Booking cancelled, Booking moved after a closure, Request for a season's space filed, Report filed, Appointment booked (the event's sandbox), Appointment cancelled (the event's sandbox), Fine paid (the event's sandbox).
- A refusal is a refused receipt, counted by its typed reason code (the action when it has none).
- Time to outcome runs from the first receipt of the same plan (the plan prepared and shown) to the outcome. A task whose plan left no earlier receipt is counted as not measured.
- A write outside an approved plan is a completed task whose receipt carries no plan hash (a request in an allocation round is sealed until the draw and has no plan). The commit paths refuse a write whose exact plan was not approved; this counts what the ledger shows, so a fault there shows here.