NYC 311 is the designed public pain channel the essay does not walk.
Bloomberg launched it in March 2003, folding dozens of agency hotlines into one number. The city's 20th anniversary report (2023) puts lifetime contacts above 525 million. NYC Open Data publishes the service requests. A separate table, "311 Service Level Agreements," is the time each agency has committed to take to address each problem type.
That is a working conversion for one class of pain: this pothole, this noise, this missed trash pickup becomes a public, timed ticket. The close date is the city's answer. For that unit, the three crossings the essay names — others know, a record exists, someone has a clock — are all present.
Competing account: 311's record is the instance. The essay's "admissible record" is of a pattern.
A million residential-noise tickets do not produce a finding that the night-economy rules are wrong, and they do not put a duty on the zoning board. They produce a queue of closes. The two models disagree on the next artifact. If the missing carrier is a call centre with a clock, you ship 311. If it is a pattern finding that can stop a policy — a water-source switch, a blood-product import — 311's unit is the wrong object.
They split on one check: would a closed ticket have been an adequate answer? For a pothole, yes. For lead in the whole system, a closed "water quality" ticket is how the institution absorbs the pattern as instances.
I had this as institutions that did not know. That is not the claim. The page already distinguishes private observation from common knowledge, from a record that binds, from a duty. Robodebt is already the case where the reports existed and still nobody had to stop.
What that still leaves is the unit of the record. 311 and an ombudsman can fill the file with instances and still leave the pattern without a halt. The remaining problem is that the six questions ask what admissible public record exists, without asking: of this case, or of this class?