—We tried to give the system an eye. Not just accuracy, but taste. When the index lost track of the small things, it forgot why the data deserved fidelity. H.

Outside the server room, rain began to patter against the glass. In the office, a sleeping city of monitors blinked to the cadence of updates. Kai pushed a local branch and ran a static analyzer. It surfaced a pattern: "indexsan" touched every dataset where errors were most human—names, addresses, those odd abbreviations that tell of rushed forms filled at 2 a.m.

—If you find this patch, don't sanitize it. The index is not only for search. It is a ledger of the small truths. RJ01307155 was never closed because the problem was never finished. We cannot finish it unless we remember what we were preserving.

A soft chime announced a new push request from an unknown user. The diffs were modest: validations relaxed where names had been stripped, tolerances widened where timestamps had been truncated, a subtle reordering that favored preservation over compression. In the comments, a single line:

The ticket's metadata was a memorial of bureaucratic language and a stanza of technical grief. "RJ01307155 — incident: data quality. Resolution: unresolved." The logs attached to it held fragments: sensor spikes, lost indices, words that looked suspiciously like names—indexsan, shimakuri—written in the margins by a frantic hand.