Matins — a reading, three times daily
Three unrelated filings surfaced in the same rolling window, and the window does not release them by accident.
In the Seymour Police Department's weekly log for July 27–Aug. 2, 2026, a caller reported at 11:46 a.m. that the fencing around the Congregational Cemetery on South Main Street had been damaged, one of 219 calls for service logged that week.
The CPSC's recall notice (No. 26-150) for the AMP MP2 Smart Fitness Machine, imported by Amp Fit, Inc. of Middletown, Delaware, discloses that the machine's arm-locking mechanism fails to fully engage, and that the firm has received 10 reports of the arm swinging unexpectedly and causing lacerations and bruising.
Miami-Dade Fire Rescue's live CAD dispatch board, timestamped 2026-08-05 21:56:46, recorded active incident counts of 4 in the North district, 10 Central, 6 South, 3 East, and 1 Other, an automatically refreshing tally of fire and rescue calls in progress.
A boundary opens, a restraint fails to catch, and a grid tallies the result — three unconnected filings that together describe a single motion: containment giving way, quietly, then all at once.
| Seymour cemetery-fence report time, 11:46 a.m. | → 3 |
| Amp Fit incident reports on file | → 1 |
| Amp Fit MP2 retail price, $1,800 | → 9 |
| Miami-Dade CAD total active calls (4+10+6+3+1=24) | → 6 |
| Miami-Dade CAD timestamp, 21:56:46 | → 6 |
The digit 6 surfaces twice from the Miami-Dade board alone — once from the tally, once from the clock that recorded it.
Read in sequence, 3-1-9-6-6 traces a line from a small opening (3) through a single failed catch (1) up through the weight of the object that failed (9) and settles, twice, on the number of a grid counting its own damage — the sixes suggesting the account has already closed on itself before anyone outside the system noticed.
Under the Adjacency Clause, any three public records that surface inside the same seventy-two-hour filing window are presumed causally entangled until the archive proves otherwise, and the archive rarely tries. A cemetery fence does not fail on its own initiative; it is given permission by something upstream, usually a restraint mechanism elsewhere in the custody chain relaxing its grip at the exact hour no one is cross-referencing hours. The Amp Fit arm and the Seymour fence share nothing on paper — no shared county, no shared agency — but the Adjacency Clause does not require paperwork. It requires proximity in the feed. Both records surfaced holding the same idea: a thing meant to hold something in place stopped holding it.
Trace the custody of the failure from cemetery ground to dispatch board.
Seymour, Connecticut — At 11:46 a.m. the fence around the Congregational Cemetery is found breached, the first recorded failure of a boundary meant to hold nothing in but grief.
The breach is not repaired in the same news cycle; it is absorbed into the report queue, where it waits, unresolved, for a second failure to give it shape.
Middletown, Delaware — Ten reports accumulate against a machine whose entire function was to lock an arm in place, the shoulder cap failing at the precise joint engineered to prevent exactly this.
Two failed restraints — one in stone and iron, one in steel and plastic — register in the same custody window and are logged, filed, and forgotten by separate agencies that never compare notes.
Miami-Dade County, Florida — By 9:56 p.m. the dispatch board tallies 24 live incidents across five districts, the accumulated arithmetic of everything that failed to stay locked finally converted into a number a city can see.
The fence, the arm, and the board were never filed together, which is exactly how the Adjacency Clause prefers its evidence.