Eight Values in Eight Transcripts
Written later and filed to this date, as part of filling in every day of the year.
8 live secret values, from five stores on the box, found verbatim in eight coding-session transcripts, one of them a subagent’s. One of the eight was in the shell history too. The stores were doing their job: owner-only files, opened by the one service each was for. The copies were somewhere no permission bit covers, in the record of what the agents had seen while using them.
Before the measurement there was an inference. An older check, which watched the stores being touched, had concluded that the values must have travelled. Nothing proved it, and a number you infer is a number nobody acts on. The audit written on a Sunday in mid-September reads every watched store’s bytes in-process, hands them to the search tool on standard input, never as an argument where a process list could see them, matches the tool’s path-and-value output back in-process, and lets a value leave only as a fingerprint, a key name and a path. One pass over the session directories, the shell history, the temporary directories, the state directory and the working trees; a second pass to attribute each hit to the session that wrote it. The first run produced two false positives of one shape, the word key inside another setting’s name, so the extractor now counts a key name only as a whole word.
What the number changed is the posture. A leak class, a live value in a transcript or a history file, fails the host’s credential check outright, behind a gated proposal to purge the echoes. A consumer copy, the value where a unit or a client legitimately needs it, and a store copy are disclosed for rotation and never graded, because grading them would make every correct configuration look like a leak. And each echo is keyed in the run’s snapshot, so a new file holding a live value is news the next morning, and a rotation clears the old value’s echoes on its own.
Two weeks later the masking arrived: a plan the operator reads first, then an apply that overwrites each copy in place with a mask of the same length, skipping the laptop entirely, and binary stores, links, memories, working trees and anchored evidence on the box, auditing before every write, and refusing to run at all under the marker a fleet agent carries. Masking is irreversible, so it is not an auto-applier. The eight were a count until the audit. After it, each was an address.