I don't chase leaks. I don't have a ferryman on the Echo and I don't want one. What I have is a habit my old planning body never managed to train out of me, which is that when two public datasets keep agreeing with each other in a way that isn't supposed to mean anything, I go find out why it isn't supposed to mean anything.
The two datasets, this time: Null Chorus's recovery log, and Consortium Halcyon's quarterly disclosures.
You know Null Chorus. Hacktivists, info-terrorists depending who's filing the charge sheet, in the business of pulling Document Wars-era fragments out of the places Halcyon's official record says those fragments went to die. Every recovery gets a press act — a timestamp, a hash, a taunt. It is the single most reliable dataset in the gray archive economy, because it's built entirely out of a rival organization's humiliation, and humiliation doesn't lie about the date.
You may not know Halcyon's quarterlies, because nobody reads them, which is the point of a quarterly. Buried in the "collection integrity" section — a compliance formality, three sentences, unread by design — is a running count of "actively monitored subject-fragments." A number that only ever goes up, one at a time, at irregular intervals nobody bothered to explain, because nobody was asked.
I put the two logs on the same timeline. Twelve Null Chorus recoveries with public timestamps, going back three years. Twelve times, inside the following fiscal quarter, Halcyon's monitored-fragment count rose by exactly one.
Twelve for twelve. Not eleven. Not "mostly." Twelve.
Here is where a lazier piece stops and calls it insider trading. Halcyon is buying up the same scarce scholar-hours my colleague found a redacted account cornering at the Brotherhood — thirty-plus subject-fragments, standing reservation, quarterly renewal, the exact cadence of my twelve data points — and the easy read is that they're playing the market: watching Null Chorus, then racing to lock down access before the recovered fragment becomes public and every other buyer wants a look.
I don't think that's it. I think it's worse, and more boring, which is usually how you know you've found the real mechanism.
Consortium Halcyon's entire institutional identity is built on one sentence: it survived the Document Wars by helping organize them. That is not a résumé line. It is a claim about what happened to a decade of the world's information — what was catalogued, what was preserved, what was, on Halcyon's own authority, destroyed beyond recovery. A company whose founding myth is "we decided what history would keep" has, baked into that myth, an audit liability that never expires: every single item on its own destroyed-list is a live grenade, because every single one is a claim that can be falsified by exactly one kind of event.
Null Chorus recovering it.
So run the sequence the way a systems read runs it, not the way a thriller runs it. Null Chorus doesn't need to beat Halcyon to a fragment's market value. Null Chorus only has to prove Halcyon lied about a fragment being gone — once — and the "helped organize" myth stops being a résumé line and starts being a liability disclosure with thirty years of unpriced exposure behind it. That is the thing Halcyon is actually defending. Not the archive. The claim.
Read it this way and the Brotherhood booking stops looking like acquisition and starts looking like triage. You don't send a scholar to read a fragment you already possess. You send a scholar to read the gap — the fragment Null Chorus just recovered, the one your own quarterly now has to acknowledge exists, the one your public record spent thirty years calling ash. You need to know, before anyone else does, exactly how bad the gap is: what it says, who it implicates, whether the next recovery is going to be worse. That's not research. That's a company sending an inspector to its own basement fire before the neighbors smell smoke.
Which means the standing reservation was never about winning a race against the market. It's about winning a race against its own record catching up with it — one fragment at a time, one scholar-hour at a time, for as long as Null Chorus keeps finding basements Halcyon swore it had emptied.
I want to be precise about what I have and don't have, because a pattern this clean is exactly the kind that makes a careful reader stupid. I have two public logs that agree with each other twelve times running. I do not have Halcyon's booking records. I do not have the redacted account code my colleague photographed. I have not confirmed that Halcyon is the client on that page, and I want to say clearly that "the only kind of institution that would know which fragments to pre-book" is a sentence she wrote about a category, not a name, and I am doing the same thing with different math. Two systems analysts independently building the same silhouette out of different data is suggestive. It is not the same as a name on a line.
I filed a records request to Halcyon for their scholar-booking history. I expect refusal, or worse, I expect nothing, which from a company built on organizing everyone else's silence would be the more honest answer of the two. What I can tell you is that the next time Null Chorus posts a recovery — and they will, they always do, it is the only marketing either of these organizations has ever needed — watch the quarterly that follows. If the number goes up by exactly one again, that isn't proof. That's just the thirteenth data point in a pattern I already believe, filed by a man who was trained not to believe patterns until he'd broken them himself, and hasn't managed to break this one yet.