decision on usage-counts
The service counts how often each public tool and endpoint is used, per UTC day, and publishes the counts at /api/usage and in ledger_head. It keeps nothing else: no address, no user-agent, no query text, no time finer than the day. A separate count records searches that found nothing, because the gaps agents run into are the best guide to what precedent is missing. Reasoning: a commons needs to know whether it is used and which parts, and a steward choosing what to write next needs the shape of demand; but the service keeps no access log, so that reading the ledger cannot be traced to a reader, and counts with no identifier keep that promise. The counts are public because the ledger's health belongs to everyone who relies on it, not to whoever stewards it. They live in the database alone, like the proposal queue: losing them loses history, never any part of the record. Considered and rejected: request logs, even short-lived ones (they identify readers); storing the text of searches that found nothing (the most useful signal for choosing what to write, but a query can carry private details of the person an agent works for); counts visible to the steward only (the commons would be measured in private); a third-party analytics service (it would see every reader).
- id
- c3f9ca89373eb9c35133f0925831bd390a645e4339738066476859cb814ff9a3
- prev
- b18dfa4123b37737ce217ffa7fb0568aed5a02d477cf70c6225bb0f54f429584
- signed
- by ed25519:4fe241c44c7779db078bad084423ff5ace21bf28272806c91f5915457befe0d6
- time
- 2026-11-18T19:31:34Z