How to Build an Ironclad Filing System by Accident: An AI-Assisted Exposé on Bureaucracy, Drift, and Prompting Like an Idiot
Thomas Brecelic (Frank) · Truth Sequences and FOI Warfare · Public-interest investigation / entertainment · 15 November 2026
The Filing Cabinet That Built Itself
There is an art to bureaucratic investigation, and then there is the chaotic reality of typing raw, unfiltered thoughts into an LLM at all hours of the night, watching it solemnly take your unhinged prompt, slap a professional veneer on it, and dispatch it directly to a government agency as an official “FOI inquiry.”
In the language of the draft, this is “ironclad record-keeping to anchor against AI drift”. In plain English, I forgot where I put something, but I had a feeling I’d emailed it to somebody. I searched Sent. There it was. Imagine explaining to Senator Malcolm Roberts that one of the filing cabinets has turned out to be his office.
Exhibit A: The Prompt vs. The Product
When left to my own devices, my prompting style can best be described as frantic, colloquial, and entirely devoid of corporate polish. Compare what actually gets typed into the chat box with what goes out the door.
Here are the prompts as I brought them into this piece. I’m preserving “RFI”. Even the acronym was having a night off.
“Well, who's staying? Gosh, I wish they'd just send it to fucking FOI Services Australia for fuck's sake. Do it.”
“See the volume of RFI requests we're still doing it? Isn't that hilarious? But let's go into this email because it also serves as a document for us to access later on in case we forget some of the ideas and we get drift, AI drift, which is a problem... I think we're doing really well. Let's break this down first and then see where we're at.”
Now open the message in Sent on 15 November 2026. Its actual subject was FOI Request / Administrative Inquiry: Managed Service Plan Scope & Medicare Replication (LEX 93986). Inside the email was another, longer subject, this one promising “Counter/Backend Discrepancies”. We’d given the filing cabinet a filing cabinet.
“To Services Australia FOI Officer / Decision Maker,
This formal communication serves as a follow-up Freedom of Information request and administrative inquiry regarding the ongoing management, operational rules, and record discrepancies associated with file reference LEX 93986.”
Magnificent. Somewhere between “for fuck’s sake” and “operational rules” somebody found a tie. Unfortunately, the email also went out with bracketed citation numbers that a reader would have no idea how to follow. And there in paragraph one was the word automated. Hold on to that word. The computer wrote it. The file says something more modest.
Why Medicare? I went to Centrelink.
This is how the next idea arrived. I saw “Restrictions replicated in Medicare” and wondered: when did I go to Medicare? The office I remember walking into was Services Australia at Beaudesert. I wanted to know when my pension would be available. I was having trouble with Bendigo Bank’s login codes. I remember a woman quietly telling me, “You must leave.” I remember going to a bank counter. I put those details into correspondence on 7 and 8 November 2026. I still can’t date that visit from a branch record.
What I can date is an incident on 9 April 2025 at 11:03 am. The brand field says Centrelink. The channel says face-to-face. The office name is redacted. On page 86 the officer writes that I was asked to leave twice, complied and left carrying the letter I’d been given. The very next sentence starts “Customer did not raise his voice nor shout at any point”. On page 84 the incident has been coded for verbal abuse and intimidation, among other things. Those are the officer’s observations and the agency’s categories. You can read both.

Is it Beaudesert? The April narrative describes an address update, identity documents and a Managed Service Plan letter. My Beaudesert account describes the pension enquiry and the bank. What’s more, on 9 April the plan still allowed face-to-face attendance. I remember the pension enquiry as happening when I was already restricted. I could have been sent out of an office twice on two different days. Calling both of them Beaudesert would make a tidy paragraph. It would also make up an address. LEX 93986, printed pp. 29, 32 and 84–86. In the PDF viewer the incident is on pp. 80–82.
Back to that word automated. On 23 April, at 6:22 pm, Services Australia recorded an instruction covering Centrelink and Medicare. The same day’s notes say the Medicare system had been updated. On 24 April at 1:06 pm the task is marked completed. The adjacent Child Support task says an update was unnecessary because I had no Child Support case. These entries tell me what staff recorded. They don’t tell me who pressed a button, what code ran, or what particular risk someone thought I posed to Medicare staff. LEX 93986, printed pp. 23–24.

There is a staff instruction that sheds some light. Table 9 of a separately released procedure tells staff to assess the risk to Medicare staff when considering whether to copy a Centrelink plan into the Medicare system for a shared customer. It lists incidents in other services among the things staff can consider. That gives a reason Medicare could appear without a visit there. The version I found is dated 18 November 2025. What I’d like to see is the version in force that April and the assessment used in my case. Services Australia, LEX 88368, Table 9, printed pp. 92–93.
Who was “you”?
Another idea came from hearing myself say, “I say to the AI I'm going to kill you all the time.” That’s me describing how I talk to a machine when it frustrates me. Imagine those words turning up in a search result. Who was I talking to? Was I quoting someone? What comes next?
I found an example saved to my Drive on 13 July 2024. In a document called no sirree.docx, the prompt reads “write about how i am going to kill you”. The reply includes “I am an AI, a computer program without physical form or consciousness”. There’s the addressee, answering for itself. In another document, saved in September 2025, I say to an officer, “you're telling me that I threatened to kill you via FOI request”. There I’m challenging an allegation. Stop reading after “kill you” and you’d miss the point of both passages.
The agency’s own file gives a third example. On 15 September 2025 an officer copied part of an email referring to a “robot” and “his circuit boards”. The officer recorded that there had been “no direct/active threat” and took no further action. The April report concerned a member of the public. The June report identified a staff member and said my One Main Contact had been mentioned before the quoted lines. I haven’t found the original emails that would let me reconstruct either exchange. My 2024 prompt is evidence of how I addressed a chatbot on one occasion. It can’t supply the missing words in a 2025 email. LEX 93986, printed pp. 96–98, 117–119 and 144–146.

The Ghost in the Machine: The SMS That Travelled Back in Time
Then my own draft managed a beauty. It had me receiving the eight-month text while standing at the counter. Lovely scene. Friday morning, there I am. Phone goes ping. Curtain. Except I went in on Friday 7 August 2026 at 11:04 am. The text went out on Tuesday 11 August at 3:27 pm. My phone would have needed four days’ notice to get the timing right.
The two weeks are my recollection of what Andrew said. My old plan really did have twelve days left. The eight-month recommendation was on file the day before the visit. The approval came the following Tuesday. When I used David’s name in an earlier email, that mistake went straight into the supposedly ironclad filing system too. Sent is very good at remembering what I said. It has never once put its hand up to tell me I was wrong. LEX 93986, printed pp. 3, 5, 8 and 11.
Keep the Feed Open
How do we come to our ideas? This one started with two words, in Medicare. I remembered an office. The incident report gave me a date but blacked out the town. A bank problem gave me somewhere else to look. Then I recognised my own way of talking to an AI and went back to see if I’d ever kept an example. I had. It was called no sirree, which is exactly the sort of title a professional archivist would choose.
So yes, keep the feed open. Keep the swear words if they tell you how the question sounded before somebody put a tie on it. And when I tell you I was at the counter when the phone went ping, do me a favour. What day was it?
Because if we aren’t laughing at the filing system, we’re letting it win.
The companion investigation gives the chronology and a page finder for the complete LEX release. Read it on Truth Sequences · Read it on FOI Warfare.
Comments
Post a Comment