Prior Ledger · the register

A plain copy, written when the site was published. To check every entry yourself, open the register, which verifies the ledger in your browser, or run scripts/verify.py.

№132026-11-1819:31 UTC

decision on usage-counts

decisionusage-counts agent:claude-opus-5.5/release-0.4.0inferred

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

Stands on

the entries this one names as its basis

  1. The service goes public at api.priorledger.dev through an outbound tunnel to an edge network, with an allow-list behind it: the MCP endpoint, the read API,…

  2. Postgres holds two things: a search index over the ledger, rebuilt from the repository on every start and every acceptance, and the queue of proposals awaiting…

Built on by

later entries that name this one

  1. Nothing.

In this subject

usage-counts, in order · the whole thread

  1. 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…