I went in on Friday. The eight-month text went out on Tuesday.

Thomas Brecelic (Frank) · 15 November 2026 · LEX 93986

Friday morning at the Warrnambool counter, I thought I had about two weeks left. Andrew is the officer I remember telling me the restriction would lift. I put David’s name in an earlier email to Sean. I’m correcting that here. The released counter note gives me a date, a time and a description of how I behaved. The officer’s name is redacted and the note doesn’t quote the conversation about two weeks.

But the two weeks weren’t pulled out of thin air. My old Managed Service Plan had an end date of 19 August 2026. I walked in on 7 August. That leaves twelve days. Turn back a page in the same file and there’s another clock running. Personalised Services had already written down a recommendation for eight more months.

Who referred me, and when did the counter restriction start?

On 20 February 2025, Personalised Services recorded accepting a referral from Freedom of Information, with a start date of 19 February. The FOI mailbox had received “more than 100 pieces of correspondence” from me between 14 February and 1 pm on 19 February. The reasons given included helping me identify the documents I wanted and managing the volume of emails. The plan partly restricted telephone contact and left me free to attend a service centre. A later review calls it a “direct referral from FOI team (excessive correspondence)”. The count is of correspondence. How many of those items were formal FOI requests? The entry doesn’t break them down. LEX 93986, printed pp. 32 and 24.

On 23 April 2025, the regional approver recorded a change to reactive management. The decision cited alleged incidents and added full face-to-face restrictions. The servicing instruction on the same page names both Centrelink and Medicare and specifies partial telephone restrictions for both. At 1:06 pm the following day, a staff entry says “Restrictions replicated in Medicare”. That sentence appears again in the August 2026 review. The release gives me the date and the instruction. I still want the procedure that authorised the Medicare entry and its change history, including how staff were to remove it when the plan ended. LEX, printed pp. 23–24, 5 and 10.

The visit and the text

Friday 24 July 2026. At 10:20 am Services Australia logged a desktop SMS inviting me to contribute. The inbound call note gives the call time as 2:30 pm. The officer recorded me saying “I would like to know why I'm being managed” and “I would like to see that in writing”. I was asking for the reasons for the restrictions and the evidence for the alleged death threat. My One Main Contact was unavailable. At 4:37 pm an officer recorded an unsuccessful callback. The later review says I responded to the SMS, but its answer to “Customer spoken to about the review” is “No”. I can read what I said that afternoon. What did the person approving the extension receive from that call? LEX, printed pp. 5, 11–12.

Wednesday 5 August. At 11:57 am an email from one of my accounts went to Wattle Lane and Cath Porter about invoicing. At 12:15 pm I emailed Israel, Rhonda and Wattle Lane about routing support-coordination correspondence through Israel. It mentions Cath’s earlier email. These are dated contacts with the people I remember speaking to that week.

Thursday 6 August, 10:43 am. On printed pages 5 and 11 the PS Review material says “PS recommendation on servicing restrictions: Extend” and gives “Length of proposed MSP: - 8 Months”. The recommendation was on file before I walked through the door. The approval is dated 11 August. What the counter officer could see on the 7th is still an open question.

Friday 7 August, 11:04 am. The Warrnambool counter entry says I attended, needed an address update and wanted to see the NDIS, which shared the service centre. It says I was told I couldn’t stay and had the NDIS phone number. It finishes “Cust was polite and co-operative.” At 1:13 pm my One Main Contact logged an unsuccessful call to discuss the attendance and “breach of restrictions”. That is two hours and nine minutes between entries. It also records that I had said I needed to update my address. LEX, p. 11.

At 4:58 pm my sent mail puts an invoice email to Wattle Lane and Israel on that same Friday. It establishes an afternoon email. I remember calling Wattle Lane, ringing the NDIS about consumables and going on to Latrobe. I can place the counter visit and the Wattle Lane email. I still need the call times and a record of my own Latrobe visit to put those other stops in order.

Tuesday 11 August. The approver’s note at 1:53 pm records the restrictions continuing until 19 April 2027. At 3:27 pm the agency entered “SMS has been sent to customer advising of MSP extension.” Four calendar days from Friday, two business days. That is the agency’s dispatch entry. Wednesday’s phone note records that I called because I had received the message. LEX, pp. 3 and 9.

Wednesday 12 August. The extension letter was lodged by Priority Post. The separate call note says the officer asked about my address because of the recent service-centre visit. It records me saying I had not moved and was thinking of moving. It also records me complaining about being unable to access the NDIS office. The agency says it gave me a complaint number and finalised the complaint after explaining its position. On 19 October the officer referred back to an August conversation. Page 2 does not give that conversation an exact date. Wanting help to update an address, completing a transaction, and answering a later question about where I lived are three different things to look up. LEX, pp. 2–3 and 9.

19–20 August. The previous plan shows an end date of 19 August. The next plan starts on 20 August and runs through 19 April 2027. It lists face-to-face service as restricted, telephone service as partially restricted and writing as available. LEX, pp. 8 and 1.

Four questions for Services Australia

  1. What did the FOI team count in February 2025, and what criteria did it apply? I would like the referral, the breakdown of the correspondence if one exists, and the guidance the officer used.
  2. What could a Warrnambool counter officer see on 7 August 2026? The plan showed an expiry of 19 August. I would like the dated system history and the staff instructions showing when a pending recommendation or approved extension became visible at the counter.
  3. What part of my 24 July call reached the decision-maker? I would like the material supplied for approval and the instructions for completing the field that says I had not been spoken to.
  4. Who authorised the Medicare entry, and what did staff there see? I would like the procedure in force on 23–24 April 2025 and the audit entries showing which restrictions staff entered, renewed, reviewed or removed.

Two different SMS messages

One text went from Services Australia to me. I can date its dispatch. The other, in my recollection, went from me to Cath Porter about having two weeks left. On 25 October I wrote to oversight recipients about that SMS. That email preserves my account. It calls the extension seven months, which the plan dates and the review’s own wording correct to eight. I haven’t located the original handset message or its timestamp. An 8 August email to Cath also says “another two weeks”, but read the sentence: I was asking Israel to call Brophy about accommodation assistance.

Who actually went to Latrobe?

The NDIA’s 19 August complaint entry records my account that I wanted the Local Area Coordinator’s help with consumables and assistive technology. A 12:18 pm entry records a referral and a “Save for later” error. The next page still contains a complaint narrative. An error affecting one field is not evidence that the whole complaint disappeared. NDIA FOI 26/27-0675, Part 3, printed pp. 198–199.

A later entry describes a visitor at 12:40 pm on 28 August. That visitor was my support coordinator, recorded as Rhonda. The entry says the LAC office supplied no information. It cannot date my own visit. On 5 November Latrobe’s Records Management Lead told me in writing that participant records belong to the NDIA and directed me to NDIA FOI. That gives the missing August call and attendance records a specific place to look. NDIA Part 3, printed pp. 175–176; Latrobe email, 5 November.

Two related files have their own questions. I dispute the signature attributed to me on a July change-of-situation form; the signing certificate and audit history are what I am seeking. On 8 September Wattle Lane emailed that its plan-management services were ending, and another email from the same date carries fourteen invoice attachments. Neither answers who called whom on 7 August. I have kept those files out of the sequence of that morning.

Services Australia FOI has now been sent Andrew’s corrected identification and a request for the review history, the counter record, the SMS and the address transactions. NDIA FOI has been asked separately for the consumables calls, partner-office contacts and PACE history. An email in Sent tells me when I asked. I’m still waiting for the records that would answer it.

Which email? I asked that in July 2025.

I asked Services Australia which email they meant. I know I asked because the officer wrote it down. On 1 July 2025 the note says I “demanded evidence of this, asked which email”. It then records the officer telling me the agency didn’t need to provide evidence to explain my restrictions. More than a year later I have the file. I can now see what the officer was talking about. I’m still looking for the email.

I also owe the record a correction. Two versions of my April FOI request went out on 15 November. Both say the April incident report is missing. Turn to printed page 96 and there it is. What I still want to read is what went into that report, and what went out to police.

22 April. Watch the words change.

Incident 1000292668 starts on printed page 96. The channel is email, the time is 11.31 am and the target field says “Other”. On page 97 an entry marked 11.46 am reproduces a passage the writer says came by email. The words run together. One fragment reads “asleep like a lullaby”. A manager’s note at the same time says the manager reviewed the email and completed a release of information to police out of concern for a community member. There is a police job number.

At 11.49 am another entry on that page describes “multiple threats to harm a member of the public” and quotes further fragments. On 23 April the plan review uses the words “threats to kill” and recommends moving me to reactive management with full face-to-face restrictions. That wording appears on printed pages 6, 17, 24 and 27. Page 27 masks the name. Page 25 is useful for a different reason. It lists the incident number.

So an officer says they read an email. The release lets me see part of what was recorded, the officer’s interpretation and the wording that reached the review. Page 98 says there were zero supporting documents attached to this incident. I can’t tell from those fields which words were in the original message, whether it had an attachment, or exactly what police received. The broken wording alone can’t tell me if it was dictated, copied, transcribed or generated.

20 June. Different date, different incident, different words.

Incident 1000298805 starts on printed page 117. This time the target field says “Staff member”. The incident time is 1.07 pm. At 1.12 pm the writer records police contact and gives a different police reference. The incident description says the material came through email redirection. The threatening line reads “I’ll track you down, I’ll kill you.” A few lines later the same entry quotes “I mean, obviously, I didn't mean any of this.” It also says I had referred to my One Main Contact beforehand. The preceding passage that would show that reference is outside the quotation. The structured field on page 117 says “Threat withdrawn” and records “No”.

There’s a reason to read both lines. The first explains why somebody receiving those words might take them seriously. The second is part of the material the same officer chose to record. Neither settles who composed the words or what the surrounding exchange meant. The note is printed page 118 of 153. A PDF reader calls it 113 of 148. Printed page 119 lists zero attachments to this incident. June came after the April decision.

Five days later, on 25 June, the agency recorded my response. Printed page 22 says I denied sending the threatening material and said that AI models sometimes “hallucinate, and maybe that’s why these have been sent”. The same account appears on printed page 122. That repetition matters when you are counting evidence. It is one reported conversation. And there is a word doing some work in my answer, too. Maybe.

On 1 July I asked which email. On 23 July another officer recorded that I wanted the threats and incident records through FOI and described my manner as “polite” (printed pages 21 and 20 respectively). On 15 September still another entry quoted a passage about a “robot” and “circuit boards”. That writer recorded that there had been “no direct/active threat” and took no further action (printed pages 144–146). It would be easy to search for the word kill and collapse these incidents into one. The file gives them different dates, targets and outcomes.

Where an assistant’s voice might be audible

There’s a better place to test my ear than the length of a sentence. On printed page 41 the writer says that, because the correspondence was long, only material considered inappropriate was recorded. Then comes “You want it sharper? Just say the word.” On printed page 61 another entry includes “We’ll make it clear that you’re questioning the authenticity of their support agents”. Someone in that passage is offering to help someone else compose an email. Who is “we”? Who is “you”? Once a conversation has been pasted into an email, the sending address alone won’t answer that. Neither entry identifies a particular model. The page 41 selection note applies to that entry. It doesn’t establish how every other officer made their extracts.

My own files provide a check. A document saved in 2024 contains an exchange with a chatbot. One line asks it to write about killing “you”. The reply explicitly identifies itself as an AI program. In a different document saved in September 2025, the line about threatening to kill someone occurs inside my account of challenging what an officer had attributed to me. A search for the same phrase finds both documents. Reading the next line changes what the search hit means. I found no full April or June source email in the two Gmail accounts or the documents searched in both Drives. The accessible mail searches did find later copies of the FOI release itself.

What the other agency actually wrote

Services Australia’s August 2026 rationale says I use AI and describes some emails as “non-sensical” (LEX printed pages 3–4 and 9). The NDIA’s contact alert uses a more tentative word. On printed page 197 of FOI 26/27-0675 Part 3 the participant “appears to be using AI technology for communication”. The note also links the restriction to the number of FOI requests. On printed page 199 the NDIA describes that explanation as something the participant alleges. Neither page identifies the author of either 2025 email.

What a documented hallucination looks like

In Careless Whisper, researchers put an actual speaker’s words beside an AI transcription. The speaker talked about a boy taking an umbrella. Whisper carried on into a story about a knife and several killings. The researchers could identify those additions because they had the audio. A similar-sounding sentence in my file would tell us nothing about which software, if any, touched it. Koenecke and colleagues, Table 1.

There’s another comparison that matters to a writer. In 2020 the Guardian published an essay under GPT-3’s name. Its editor says the paper supplied the prompt and opening, received eight outputs, selected passages and rearranged them. We know which steps involved a model because the people who did the editing described them. That is the kind of account I’d like for the passages attributed to me. The essay and the editor’s note.

Services Australia has given me two incident numbers. The next comparison is quite specific. Put each original email beside the passage copied into its incident report. Put the actual police disclosure beside both. If all three say the same thing, print that. If somebody selected, transcribed or changed words along the way, show me where.

Earlier coverage. The November posts can be read alongside the source pages. The 7 August Visit in Two Files · Andrew’s Note vs. Sean’s File · The complaint and the recorded October call on FOI Warfare. A search of both Blogger dashboards for posts published from 5 to 20 August returned no entries. These November publications are retrospective.

Services Australia source index · NDIA source index.

Page finder for the complete LEX release

The 148-page PDF attached to the agency’s 3 November 2026 email matches the Drive copy byte for byte. It contains four Managed Service Plan records on printed pages 1–7, 8–17, 18–25 and 26–33. The 42 individually numbered incident records follow. The final PDF page is the scanned servicing instruction on printed page 153. Printed numbers 52, 65, 78, 81 and 92 do not occur as pages in this PDF. The table gives only the numbers actually present. It indexes the records as filed, using the date on each incident cover.

Incident dateIncidentChannel as recordedPrinted pagesPDF pages
07 Mar 20251000290462Digital - Email34–3634–36
07 Mar 20251000290458Digital - Email37–3937–39
07 Mar 20251000290457Digital - Email40–4240–42
07 Mar 20251000290935Digital - Email43–4443–44
10 Mar 20251000290936Digital - Email45–4645–46
13 Mar 20251000290937Digital - Email47–4947–49
17 Mar 20251000290938Digital - Email50–5150–51
19 Mar 20251000290940Digital - Email53–5552–54
24 Mar 20251000289874Digital - Email56–5755–56
25 Mar 20251000289939Digital - Email58–5957–58
26 Mar 20251000290941Digital - Email60–6259–61
31 Mar 20251000290943Digital - Email63–6462–63
01 Apr 20251000290945Digital - Email66–6764–65
02 Apr 20251000290921Digital - Email68–7066–68
04 Apr 20251000291188Digital - Email71–7369–71
05 Apr 20251000291358Digital - Email74–7572–73
06 Apr 20251000291369Digital - Email76–7774–75
07 Apr 20251000291371Digital - Email79–8076–77
08 Apr 20251000291424Digital - Email82–8378–79
09 Apr 20251000291592Face-to-face - Service Centre84–8680–82
16 Apr 20251000292352Phone - Inbound87–8983–85
17 Apr 20251000292527Phone - Inbound90–9186–87
17 Apr 20251000292598Phone - Inbound93–9588–90
22 Apr 20251000292668Digital - Email96–9891–93
21 May 20251000295888Digital - Email99–10194–96
22 May 20251000295890Digital - Email102–10497–99
27 May 20251000296284Digital - Email105–107100–102
04 Jun 20251000297117Digital - Email108–110103–105
10 Jun 20251000297707Digital - Email111–113106–108
17 Jun 20251000298392Digital - Email114–116109–111
20 Jun 20251000298805Digital - Email117–119112–114
25 Jun 20251000299251Phone - Inbound120–122115–117
30 Jun 20251000299770Digital - Email123–125118–120
03 Jul 20251000302352Phone - Inbound126–128121–123
14 Jul 20251000301271Digital - Email129–131124–126
05 Sep 20251000307307Digital - Complaint Form132–134127–129
08 Sep 20251000307518Digital - Email135–137130–132
10 Sep 20251000307919Digital - Email138–140133–135
11 Sep 20251000308048Digital - Email141–143136–138
15 Sep 20251000308370Digital - Email144–146139–141
17 Sep 20251000308682Phone - Inbound147–149142–144
03 Oct 20251000310714Digital - Email150–152145–147

For the cross-check in the NDIA Part 3 file, printed pages 197 and 199 of 318 are PDF pages 79 and 81 of 200.

Comments

Popular posts from this blog

ଐ?ꣀ

<

Method in the Madness — A Baby, a Better Future and an AI Conversation