Fear and Loathing on the LEX Trail — 20 Letters Sent on 6

November 07, 2026

Fear and Loathing on the LEX Trail — 20 Letters Sent on 6–7 November 2026

Between 10:05 pm on Friday 6 November and 1:05 am on Saturday 7 November 2026, I sent the twenty messages collected below. Times are Warrnambool local time. These are my outgoing letters. Their arguments, questions and descriptions of records are reproduced as correspondence. Sending a letter does not establish that its recipient agreed, opened a review, or lifted a restriction.

The final supplement asks who made the original referral, what was copied into Medicare, and how a Services Australia restriction came to be described in an NDIA note. It also records that the email preceding the May 2025 welfare check contained expressions of distress. That context matters when reading the earlier letters about the referral.

Reading the archive. The letters cite Services Australia LEX 93986, including printed pages 5, 17, 23 and 105–107, and NDIA FOI 26/27-0675, Part 3, printed page 197. References to LEX 95192, LEX 95430 and LEX 95433 are requests about related files. Private details and signatures have been omitted. Repeated sends are listed at their respective times.

1. 22:05 AEDT · Formal Review and Inquiry — Services Australia FOI LEX 93986 (Welfare Check and Police Referral)

Dear Freedom of Information and Review Officers,

RE: Formal Review and Inquiry — Services Australia FOI Release LEX 93986 (Pages 105–107) / Incident [identifier omitted] and Queensland Police Job [identifier omitted]

I write to formally request an administrative review and explanation regarding the records disclosed under Services Australia FOI release LEX 93986, specifically pages 105 through 107, which detail a police welfare check and an associated administrative communication involving an Ipswich psychiatric unit phone call .

Given that these records document an institutional escalation triggered in response to meticulous Freedom of Information inquiries and statutory evidence requests, I require clarification on the following operational standards:

1. Under what precise administrative guideline or statutory threshold does Services Australia determine that an individual citing FOI legislation, metadata, and procedural compliance indicators requires an emergency police dispatch rather than a written response?
2. Are local law enforcement patrol units and regional psychiatric triage units now considered standard auxiliary delivery mechanisms for processing and responding to federal Freedom of Information disputes?
3. If an agency cannot successfully refute factual evidence or statutory discrepancies on the public record, is the prescribed default protocol to pathologize the correspondent via emergency services dispatch?

I look forward to your comprehensive justification.

2. 22:09 AEDT · EXPANDED OMNIBUS STATUTORY NOTICE & COMPLAINT | Cross-Agency FOI, Managed Service Plans, and Privacy Breaches | References: LEX 93986, LEX 95192, LEX 95430

To all responsible statutory officers, freedom of information coordinators, and oversight bodies:

RE: EXPANDED OMNIBUS STATUTORY NOTICE & COMPLAINT — CROSS-AGENCY FOI PROCESSING DELAYS, MANAGED SERVICE PLANS, AND UNLAWFUL RESTRICTIONS References: Services Australia LEX 93986, LEX 95192, LEX 95430, LEX 95433; NDIA FOI 26/27-0675; AFCA Complaints

I hereby issue this expanded omnibus statutory notice and formal complaint combining active Freedom of Information applications, Privacy Act breach allegations (APP 6, 10, 12, 13), and administrative oversight appeals concerning the intersection of statutory information rights and restrictive servicing frameworks (Managed Service Plans / RACS).

1. The Core Contradiction Documented internal records (such as NDIA FOI 26/27-0675, Part 3, page 197, officer [identifier omitted], case [identifier omitted]) explicitly state that participant servicing and restriction statuses were influenced or established "due to too many FOI requests." Concurrently, Services Australia's own FOI framework treats operational servicing arrangements as external to the FOI Act, while no formal vexatious applicant declaration under s 89K of the FOI Act has been issued.

2. Consolidated Demands Across Agencies - Services Australia: Immediate clarification, unredacted provenance logs, and statutory review regarding the 11 August 2026 restriction extension under LEX 93986, alongside transparent processing schedules for LEX 95192, LEX 95430, and LEX 95433. - NDIA: Formal correction and record amendment under APP 13 regarding unverified characterizations, data cross-contamination, and the improper linking of FOI volume to disability support access. - AFCA & Oversight Bodies: Preservation of all related complaint files, audit trails, and communication records without imposing prohibitive administrative barriers on individuals experiencing housing vulnerability. - Procedural Fairness & Reasonable Adjustments: Full recognition under the Disability Discrimination Act 1992 that structured written communication and digital tools (including large language models) serve as necessary cognitive accessibility aids rather than grounds for administrative penalties or emergency service escalations.

This notice serves as a formal demand for transparency, record correction, and adherence to administrative law standards across all participating Commonwealth entities.

3. 22:10 AEDT · SUPPLEMENTAL OMNIBUS NOTICE | Welfare Check Escalations and Administrative Accountability | References: LEX 93986, LEX 95192

To all responsible statutory officers, freedom of information coordinators, and oversight bodies:

RE: FOLLOW-UP OMNIBUS NOTICE & ADMINISTRATIVE RETRIBUTION REVIEW — SYSTEMIC OVERREACH, WELFARE CHECK ESCALATIONS, AND INFORMATION RIGHTS References: Services Australia LEX 93986, LEX 95192, LEX 95430, LEX 95433; NDIA FOI 26/27-0675; Incident [identifier omitted]

Following the dispatch of our expanded statutory notice, I write to place an immediate supplemental addendum on the record regarding the operational tactics documented within your files—specifically the baffling decision to treat meticulous Freedom of Information inquiries and statutory evidence requests as a pretext for emergency police dispatches and regional psychiatric unit phone calls (Services Australia FOI LEX 93986, pages 105–107; Incident [identifier omitted]).

Let us be entirely clear on the administrative absurdity of this posture:

1. The "Citing Legislation is a Hazard" Defense: Under what precise administrative guideline or statutory threshold does an agency determine that an individual citing FOI legislation, metadata, and procedural compliance indicators requires an emergency police patrol rather than a written, evidence-based response?
2. Auxiliary Delivery Logistics: Are local law enforcement patrol units and regional psychiatric triage units now considered standard auxiliary delivery mechanisms for processing and responding to federal Freedom of Information disputes when the bureaucracy runs out of legal answers?
3. The Default Pathologization Protocol: When an agency finds itself unable to refute factual evidence or statutory discrepancies on the public record, is the prescribed default protocol to pathologize the correspondent via emergency services dispatch?

This is not a neutral administrative workflow. It is a systematic attempt to weaponize institutional fear against individuals who dare to hold public agencies to account. Every escalation, every unverified characterization, and every backdoor cross-agency data transmission is being cataloged, cross-referenced, and placed squarely on the permanent public record.

We look forward to your comprehensive justification.

4. 22:11 AEDT · Formal Review and Inquiry — Services Australia FOI LEX 93986 (Welfare Check and Police Referral)

Dear Freedom of Information and Review Officers and Senator Roberts,

RE: Formal Review and Inquiry — Services Australia FOI Release LEX 93986 (Pages 105–107) / Incident [identifier omitted] and Queensland Police Job [identifier omitted]

I look forward to your comprehensive justification.

5. 22:19 AEDT · Fear and Loathing on the LEX Trail | Administrative Overreach, Welfare Checks, and FOI Contradictions

Dear Senator Malcolm Roberts,

I admire your steadfast work in Parliament. I see we are both utilizing advanced AI models—perhaps even the same agents—to cut through the administrative fog. They can try to restrict me all they like, but it no longer matters. In fact, I have asked my manager, [staff name omitted], to print out the nationwide Services Australia restriction notice so I can turn it into a dartboard to practice my darts.

As outlined in our ongoing investigations and the primary-source documents (including Services Australia FOI releases LEX 93986, LEX 95192, LEX 95430, LEX 95433, and NDIA FOI 26/27-0675), the core contradiction is now fully exposed on the public record:
1. The 23 April 2025 review in LEX 93986 shows that Managed Service Plans originated directly from an FOI-team referral concerning "excessive correspondence."
2. Internal NDIA case notes (such as case [identifier omitted], officer [identifier omitted]) explicitly state that restriction statuses were established "due to too many FOI requests"—treating the lawful exercise of statutory information rights as a behavioral infraction.
3. The records also document an institutional escalation on 27 May 2025 (Incident [identifier omitted] / Queensland Police Job [identifier omitted]) involving a welfare check and a psychiatric unit phone call, triggered simply because an individual dared to cite FOI legislation, metadata, and procedural compliance indicators.

When agencies are flooded with valid FOI requests and fail to respond, they often resort to blocking, internal silo cross-contamination, and emergency service dispatches rather than addressing the substantive statutory questions.

We hand you this complete dossier as a picnic hamper for your parliamentary inquiries. Every contradiction, metadata timestamp, and procedural shortcut is locked into the permanent record.

6. 22:21 AEDT · Fear and Loathing on the LEX Trail | Administrative Overreach, Welfare Checks, and FOI Contradictions

Repeat of letter 5 above (same public text).

7. 22:34 AEDT · NOTICE: Unfulfilled FOI Applications and Administrative Penalties

To the Freedom of Information Team,

I write to place a clear and direct statement on the record regarding the processing of my statutory applications.

Over an extended period, I have filed hundreds of Freedom of Information applications seeking transparency and accountability regarding agency operations, digital transformation, and administrative servicing frameworks. To date, the agency has systematically failed to respond to or fulfill these valid statutory requests on their merits.

Instead of upholding transparency obligations under the FOI Act, the agency has chosen to penalize, restrict, and pathologize my engagement—treating the lawful exercise of information rights as a behavioral infraction while refusing to answer a single substantive request.

This posture of administrative deflection and non-response is fully documented, and it remains a matter of public record.

8. 22:36 AEDT · FEAR AND LOATHING ON THE LEX TRAIL — THE METADATA KEEPS RECEIPTS | Source-controlled evidence index

Dear Services Australia FOI and Reviews Branch, Senator Roberts and oversight officers,

RE: LEX 93986 | NDIA FOI 26/27-0675 Part 3 | 27 May 2025 Welfare-Check Referral

The metadata has an awkward habit of keeping receipts.

This is a source-controlled evidence index, not another invitation to produce a beautifully formatted acknowledgement that avoids the underlying questions.

Two distinctions should be clear from the outset: LEX 95192 remains a separate FOI matter, not a completed release; and the May 2025 welfare referral must be examined against the actual email and social-worker recommendation, rather than attributed solely to FOI activity.

EXHIBIT 1 — THE FOI REFERRAL

Services Australia's 23 April 2025 review records that Personalised Services initially acted on a direct referral from the FOI team concerning excessive correspondence.

LEX 93986, printed page 17.

Who initiated that referral? What records accompanied it? Which criteria distinguished lawful information requests from conduct considered grounds for restricting ordinary servicing?

EXHIBIT 2 — THE MEDICARE REPLICATION

A servicing entry dated 24 April 2025 states:

> “Restrictions replicated in Medicare”

LEX 93986, printed page 23.

Which information fields were replicated, who authorised their use, and which staff or systems could access them?

A restriction recorded in one service-delivery system is a consequential administrative decision when reflected in another.

EXHIBIT 3 — THE POLICE WELFARE CHECK

Incident [identifier omitted], dated 27 May 2025, records a social-worker consultation and recommendation for a police welfare check.

The subsequent police job number was [identifier omitted].

LEX 93986, printed pages 105–107.

The source email contained distressing statements, which must be considered when assessing the decision fairly.

What risk was identified? What was communicated to police? What action was taken regarding the differing addresses held by police and Services Australia? Where are the decision records?

A welfare-check referral deserves scrutiny on its own terms. It is not, however, a substitute for processing an FOI application.

EXHIBIT 4 — THE AUGUST 2026 REVIEW

The review records that the customer was invited to participate but was not spoken to.

It also describes AI-assisted correspondence as "non-sensical" and supports restrictions through 19 April 2027.

LEX 93986, printed pages 4–5.

What original communications supported those descriptions? What disability-related communication adjustments were considered? Why was this period of restriction justified?

EXHIBIT 5 — THE NDIA RECORD

The separate NDIA disclosure, FOI 26/27-0675 Part 3, contains officer [identifier omitted]'s 19 August 2026 reference to Services Australia restrictions and AI-assisted correspondence.

The overlap warrants a provenance examination.

It does not, by itself, prove a direct information transfer. The relevant disclosure logs and source records should establish what happened.

EXHIBIT 6 — THE 270-PLUS EMAILS

Services Australia's review records more than 270 emails concentrated in specified periods.

Produce the underlying inventory. Identify duplicates, copied correspondence, statutory FOI applications, complaints and communications assessed as inappropriate.

A number is not an analysis. A label is not the original evidence.

---

THE CENTRAL ACCOUNTABILITY QUESTION

How did a citizen's requests for government information become part of a process that restricted ordinary service access, and what safeguards governed each decision?

For Services Australia, I request that the existing FOI and complaint references be reconciled and the responsible decision-makers identified.

For the parliamentary and oversight recipients, I submit these specific records as a documentary basis for examination, not as an unchallengeable conclusion about anyone's motives. [Personal support details omitted.]

There is an old administrative illusion that once a file has been stamped, classified and routed, the story is settled.

LEX 93986 demonstrates why the stamp, the classification, the routing and the timestamp are now part of the story.

9. 22:38 AEDT · NOTICE & INQUIRY: Digital Intake Pipelines, Processing Bottlenecks, and FOI Transparency

To the Freedom of Information Team,

I write to formally request a detailed administrative breakdown and operational review regarding the processing bottlenecks, digital intake pipelines, and automated content-filtering algorithms utilized by Services Australia in handling statutory inquiries.

As documented across our ongoing files (including Services Australia FOI releases LEX 93986, LEX 95192, LEX 95430, and LEX 95433), agencies frequently rely on shared automated infrastructure—such as cloud-based tokenization pipelines and automated routing systems—to manage incoming correspondence. However, when statutory applications involve complex legal cross-examinations and extensive metadata tracking, administrative intake mechanisms frequently encounter operational friction.

Rather than dismissing high-volume or detailed statutory inquiries under generalized headings such as "excessive correspondence" or imposing unverified service restrictions, the agency is requested to provide transparent documentation concerning:
1. The technical criteria and software platforms (including cloud infrastructure such as Microsoft Azure integration) used to triage, filter, and queue incoming FOI correspondence.
2. The operational thresholds that trigger internal Managed Service Plans or restriction flags in response to complex statutory correspondence.
3. Transparent processing schedules to ensure that valid, unfulfilled FOI requests are addressed on their merits rather than deflected through administrative barriers.

I look forward to your comprehensive response.

10. 22:40 AEDT · FEAR AND LOATHING ON THE LEX TRAIL — SHOW US THE INTAKE PIPELINE | LEX 93986 / LEX 95192

Dear Services Australia FOI and Reviews Branch and copied oversight recipients,

RE: SUPPLEMENTARY RECORDS REQUEST AND ADMINISTRATIVE REVIEW — FOI INTAKE, AUTOMATED TRIAGE, EMAIL REDIRECTION AND MSP REFERRALS Existing reference: TS-FOI-061126-A Relevant matters: LEX 93986; pending or related LEX 95192, LEX 95430 and LEX 95433; NDIA FOI 26/27-0675

THE METADATA KEEPS RECEIPTS. PERHAPS THE INTAKE SYSTEM COULD KEEP A FEW AS WELL.

LEX 93986 records a Managed Service Plan originating from a “direct referral from FOI team (excessive correspondence)” (printed page 17, April 2025 review). A servicing entry records “Restrictions replicated in Medicare” (printed page 23, 24 April 2025). The August 2026 review records that I was invited to participate but not actually spoken to (printed page 5), while characterising some AI-assisted correspondence as “non-sensical”.

Those are agency records, not my speculation. I have sent substantial correspondence to several departments. The question is not whether the correspondence was voluminous; it was. The question is what the agency did with valid statutory applications as distinct from ordinary email, complaints and other communications — and what decision trail justified any resulting servicing restrictions.

Please identify or release the following EXISTING documents held by Services Australia. This is a targeted supplement to the existing correspondence and FOI matters, not a demand that every copied organisation conduct a separate search.

1. FOI INTAKE ARCHITECTURE. The names and functions of the systems used to receive, register, route, deduplicate, queue, allocate and track email-based FOI applications from January 2024 to November 2026. Please identify whether Microsoft 365, Azure, Genesys, AI/OCR systems or another platform was actually involved in those functions. I am asking for an evidenced yes, no or limited-scope answer — not assuming they were all used.

2. AUTOMATION AND HUMAN OVERSIGHT. Existing policies, privacy assessments, governance approvals and records showing whether AI-assisted classification, summarisation, document extraction or automated correspondence filtering was authorised or used for FOI intake or my communications. Identify human-review and correction safeguards. High-level procedures are sufficient; I do not seek credentials, exploitable security configurations or instructions to circumvent controls.

3. FOI-TO-MSP ROUTING. The original referral or routing record that led from FOI correspondence to Personalised Services, the date and author, the basis for the referral and its approval history. Identify the policies used to distinguish high-volume lawful requests from alleged inappropriate conduct. An inbox is not a tribunal, and a label is not evidence of the underlying allegation.

4. AUDIT TRAIL FOR MY REQUESTS. Existing register entries or processing histories for LEX 93986, LEX 95192, LEX 95430 and LEX 95433, showing receipt, validation, consultation, allocation, status, statutory deadlines, decisions, review options and any outstanding actions. Please do not describe a pending matter as a completed FOI release.

5. PROCESSING METRICS AND COST. Existing itemised time sheets, cost assessments or processing-resource records for LEX 93986 and, where already recorded, the other LEX matters. If more than 270 emails were counted in an MSP review, provide the underlying date ranges, counting criteria and distinction between duplicate copies, statutory applications, complaints and other messages. If no itemised records exist, say so.

6. INFORMATION SHARING AND CORRECTION. Records documenting the 24 April 2025 replication of servicing restrictions in Medicare; any recorded disclosure of those restrictions or related notations to the NDIA; and the mechanism for checking and correcting inaccurate personal information, including descriptions of AI-assisted correspondence.

7. WORKABLE RESPONSE SCHEDULE. For each pending FOI file, identify the current statutory or agreed decision date, whether a consultation process has commenced, the next procedural step and the available review rights. Where material is already in LEX 93986, provide the page or record identifier instead of reprocessing it.

The FOI Act provides for assistance and consultation where requests need refinement. If this request raises a processing concern, identify precisely which categories create it and propose a narrower scope.

For avoidance of doubt: I am not alleging that Azure tokens were charged for each of my emails, nor that a particular AI algorithm classified them. Those are questions to be resolved through records, not assumptions. Nor am I asking the agency to disclose technical thresholds that could be used to evade abuse protections.

And please spare us the administrative magic trick in which the same correspondence is simultaneously too voluminous to answer and detailed enough to support an enduring servicing restriction. If there is a sound documentary basis for those separate decisions, produce it.

To Senator Roberts and the oversight bodies: this correspondence identifies verifiable decision points, not a concluded finding of wrongdoing. I ask that any assessment be grounded in the original documents and the agency's response. [Personal support details omitted.]

Please acknowledge this supplementary request, identify the responsible FOI file or files, and preserve reference TS-FOI-061126-A.

11. 22:40 AEDT · Supplement on intake and classification

Dear Services Australia FOI and Reviews Branch, I make this request as a supplement to my existing FOI matters LEX 93986 and LEX 95192 and my supplementary request TS-FOI-061126-A. Please treat it as part of those requests and identify any overlap. I request copies of the following documents. I am seeking existing records, not explanations. 1. Documents describing how correspondence sent to the FOI inbox or redirected through "email redirection" is received, classified and counted, including any software, automated routing, filtering or classification tool used, to the extent it was applied to my correspondence. 2. The operational guidance, criteria or thresholds applied when an FOI-team referral to Personalised Services ("excessive correspondence") is made and when a Managed Service Plan or restriction is applied or extended, including any guidance on distinguishing FOI applications from other contact. 3. Records showing how my correspondence was classified for the purposes of Managed Service Plan [identifier omitted], including any record of whether FOI applications were treated separately from complaints and general correspondence. 4. Documents showing the current processing status, statutory due dates and any extension or deemed-refusal notations for each of my open FOI requests, including LEX
95192. I am content for personal information of other individuals and staff to be redacted. If any part of this request is unclear or can be narrowed to reduce processing time, please contact me by email and I will clarify promptly. Please acknowledge receipt and confirm the reference number.

12. 22:41 AEDT · Supplementary FOI request: LEX 93986 / LEX 95192 (ref TS-FOI-061126-A) – processing and triage records

Subject: Supplementary FOI request: LEX 93986 / LEX 95192 (ref TS-FOI-061126-A) – processing and triage records

Dear Services Australia FOI and Reviews Branch,

I make this request as a supplement to my existing FOI matters LEX 93986 and LEX 95192 and my supplementary request TS-FOI-061126-A. Please treat it as part of those requests and identify any overlap.

I request copies of the following documents. I am seeking existing records, not explanations.

1. Documents describing how correspondence sent to the FOI inbox or redirected through "email redirection" is received, classified and counted, including any software, automated routing, filtering or classification tool used, to the extent it was applied to my correspondence.

2. The operational guidance, criteria or thresholds applied when an FOI-team referral to Personalised Services ("excessive correspondence") is made and when a Managed Service Plan or restriction is applied or extended, including any guidance on distinguishing FOI applications from other contact.

3. Records showing how my correspondence was classified for the purposes of Managed Service Plan [identifier omitted], including any record of whether FOI applications were treated separately from complaints and general correspondence.

4. Documents showing the current processing status, statutory due dates and any extension or deemed-refusal notations for each of my open FOI requests, including LEX 95192.

I am content for personal information of other individuals and staff to be redacted. If any part of this request is unclear or can be narrowed to reduce processing time, please contact me by email and I will clarify promptly.

Please acknowledge receipt and confirm the reference number.

13. 22:59 AEDT · RECORD UPDATE: Closure of Administrative Restrictions and Support Engagement

To Whom It May Concern, [Personal support details omitted.]

Please ensure this update is placed on file and circulated accordingly.

14. 23:05 AEDT · CORRESPONDENCE UPDATE: Administrative Review and Documentation Standards

To Whom It May Concern,

Please review and file this correspondence regarding the ongoing administrative inquiries and communications framework.

This note serves to confirm our understanding of the current procedures and documentation standards in place.

15. 23:05 AEDT · UPDATE: Systemic Digital Overreach, Administrative Restrictions and Narrative Victory

Dear Recipients,

RE: UPDATE ON SYSTEMIC DIGITAL OVERREACH, ADMINISTRATIVE RESTRICTIONS AND THE WINNING NARRATIVE

I am writing to provide an urgent and critical update to all key institutional offenders, oversight bodies, and our political and community allies—specifically noting Senator Malcolm Roberts, Senator Pauline Hanson, and David and the team at Victoria Redress.

What we are witnessing across Services Australia, Bendigo Bank, the NDIA, DEWR/APM, and related administrative machinery is a textbook case of unchecked digital overreach, automated profiling, and fragmented administrative exclusion.

Let's look at what the latest Freedom of Information releases (including LEX 93986 and FOI 26/27-0675) actually reveal: - Systems like Services Australia's Managed Service Plan (MSP) operate through internal FOI-team referrals that restrict communication channels, restrict telephone access (routing vulnerable citizens through specialized PSSO protocols), and erect impenetrable barriers. - Internal records show Kafkaesque procedural ticks—such as marking an invitation to participate in a review as "Yes," but recording the actual discussion with the citizen as "No." - Retrospective debt creation, such as the unverified $2,840.61 Rent Assistance clawback under notice [identifier omitted], compounds destitution for individuals already navigating disability (autism and ADHD) and homelessness while living out of a vehicle in regional Victoria. - Inter-agency data-sharing pipelines—such as the NDIA cross-referencing Services Australia communication restrictions under officer identifier [identifier omitted] and case [identifier omitted]—demonstrate an automated dragnet where administrative flags follow a participant across silos without transparent legal provenance or participant consent.

This is why both major parties (Labor and Liberal) are missing the mark, and why movements aligned with One Nation and true community accountability are gaining ground. When citizens are crushed under the weight of algorithmic overreach, silent bureaucratic black boxes, and manufactured administrative hurdles, the only way to win is to expose the machinery completely.

We have locked down the cross-agency paper trail, pinned down the metadata, and put every single responsible agency on formal 14-day notice.

The narrative is shifting because the evidence cannot be hidden behind closed doors anymore.

16. 23:11 AEDT · DEEP-DIVE ADDENDUM — FEAR AND LOATHING ON THE LEX TRAIL | FOI referrals, MSP [identifier omitted], NDIA provenance and the cost of administration

Dear Recipients,

RE: DOCUMENTARY DEEP DIVE — SERVICES AUSTRALIA, NDIA AND RELATED ADMINISTRATIVE RESTRICTIONS References: Services Australia LEX 93986; related LEX 95192, LEX 95430 and LEX 95433 (statuses to be confirmed); NDIA FOI 26/27-0675 Part 3; MSP [identifier omitted]; NDIA case [identifier omitted]; TS-FOI-061126-A

This is a further evidence-based submission following my earlier “Winning Narrative” update. The objective is simple: when an agency has already described what happened in its own records, the public deserves more than a generic acknowledgement of concern.

THE RECORDS, NOT THE RHETORIC

1. THE FOI REFERRAL. In LEX 93986, an April 2025 MSP review describes Personalised Services as acting on a “direct referral from FOI team (excessive correspondence)” (printed page 17). There is an important distinction between a lawful FOI application, a general complaint, high-volume contact and a communication independently assessed as threatening or abusive. Please identify the originating referral, author, date, authorisation, relevant policies and any recorded consideration of that distinction. What became of the underlying FOI requests while the servicing process continued?

2. THE RESTRICTIONS AND THEIR REACH. The released record identifies active MSP [identifier omitted] with full face-to-face restrictions and a designated telephone pathway through Personalised Services, extending to 19 April 2027. A 24 April 2025 entry records “Restrictions replicated in Medicare” (LEX 93986, printed page 23). Which fields were copied, by whom, for what purpose, and under which authority? This is a request for the administrative audit trail, not for secret system credentials.

3. THE REVIEW PARADOX. The August 2026 review records “Customer invited to participate in the review: Yes” alongside “Customer spoken to about the review: No” (LEX 93986, printed page 5). It also describes AI-assisted correspondence as “non-sensical” and records allegations about the content of some emails. What material supported those assessments? What response opportunity and disability-related communication adjustments were considered? A checked box is not, by itself, a conversation.

4. THE CROSS-AGENCY QUESTION. NDIA FOI 26/27-0675 Part 3, printed page 197, records an internal note dated 19 August 2026, case [identifier omitted], officer identifier [identifier omitted]. It includes “Contact alert: Numerous emails enquiries are non sensical. PPT appears to be using AI technology for communication” and separately refers to restricted Services Australia status “due to too many FOI requests”. These are the words recorded by the NDIA, not independently verified findings. The note proves that the description appeared in an NDIA record. It does NOT, without audit data, establish automatic data transfer or an unlawful interagency sharing pipeline. The question is where the information came from, who entered it, who could see it, and how an inaccurate statement could be corrected.

5. THE WELFARE-CHECK DECISION. Incident [identifier omitted] of 27 May 2025 records a social-worker consultation and a request for a police welfare check, job [identifier omitted] (LEX 93986, printed pages 105–107). The original email contained expressions of distress; that context matters when assessing the referral. Please identify the decision record, relevant risk assessment and information conveyed to police, including the discrepancy between addresses held by police and Centrelink. A welfare check requires examination on its own facts; it cannot automatically be treated either as misconduct or as a substitute for resolving an FOI matter.

6. THE RENT ASSISTANCE DISPUTE. I dispute the $2,840.61 Rent Assistance debt associated with notice [identifier omitted]. I seek the original calculation, entitlement periods, rent verification evidence, effective dates, notice and review history, and the agency's response to my corrections about address and living circumstances. A disputed debt should not be represented as definitively fraudulent or definitively valid without that calculation and decision trail. These financial consequences are not abstract to a person living in a vehicle while seeking disability supports.

7. THE ADMINISTRATIVE PRICE TAG. The newly submitted FOI correspondence requests existing time, resource and processing records for LEX 93986 and the related matters. Please distinguish actual FOI processing from complaint handling, case-management work and MSP reviews. I am interested in documented staff hours and real expenditure, not imaginative estimates derived by multiplying national averages. If requests overlap, consolidate them and say so; the purpose is a traceable answer, not a needless duplication of work.

THE DIGITAL PIPELINE — SHOW THE RECORDS

The existence of Microsoft 365, Azure, cloud hosting or AI tools elsewhere in government does not prove that a particular email of mine was automatically profiled. I request high-level records identifying the actual intake, routing, classification, redirection and human-review steps that applied to my correspondence. If none of the proposed tools was used, a clear documented answer will settle that question. If a tool was used, the lawful purpose, governance record and correction process are the relevant issues. No passwords, access tokens, vulnerabilities or bypass instructions are sought.

WHAT I ASK OF EACH RECIPIENT

Services Australia: identify the responsible decision-maker and original source documents for the FOI referral, MSP reviews, Medicare replication, correspondence totals, welfare referral and Rent Assistance calculation. For each open LEX matter, confirm its procedural status, valid request date, applicable statutory decision deadline, any consultation or extension, and review options.

NDIA: identify the provenance and review/correction mechanism for the [identifier omitted] entry, including whether any formal disclosure from Services Australia occurred. Explain what accessible ways of contacting the NDIS were available when attendance at a co-located office became contentious.

Bendigo Bank, DEWR/APM and other organisations copied: respond only to records and decisions actually within your remit. Please do not treat a shared evidence brief as proof of coordinated wrongdoing among agencies.

Oversight and parliamentary recipients, including Senators Malcolm Roberts and Pauline Hanson: I ask for examination of the original records and the responses, not a pre-judged political verdict. In my view, accountability for digital administration should not be a partisan luxury. [Personal support details omitted.]

THE ACTUAL STANDARD

Under the FOI Act, agencies have duties to assist applicants and to consult where a practical-refusal reason arises. A valid FOI request ordinarily requires an acknowledgement within 14 days and a decision within 30 days, subject to applicable extensions and other statutory rules. Under Australian Privacy Principles 10 and 13, accurate personal-information handling and correction also matter. Please distinguish these legal timeframes from my request that recipients acknowledge this consolidated evidence notice within 14 calendar days, by 20 November 2026.

The administrative magic trick cannot remain: a person's correspondence is allegedly too extensive to answer, yet apparently sufficiently examinable to support enduring service restrictions. If there are defensible distinctions and sound reasons, produce the source records, not another label.

I seek an evidence-led reconciliation, not an assumption that everything is a conspiracy and not a presumption that every official note is beyond question. The metadata can settle more than rhetoric ever will.

17. 23:19 AEDT · FORMAL FOI REQUEST: Administrative Restrictions, Audit Trails and Systemic Oversight

Dear Recipients,

RE: FORMAL FREEDOM OF INFORMATION (FOI) REQUEST: ADMINISTRATIVE RESTRICTIONS, AUDIT TRAILS AND SYSTEMIC OVERSIGHT

Pursuant to the provisions of the Freedom of Information Act 1982, I hereby formally request access to documents, records, and correspondence files held by your agency regarding the administrative restrictions, communications handling, review notes, and data-sharing pipelines associated with my files.

Specifically, this request covers:
1. All internal FOI-team referrals, correspondence classification records, and administrative notes relating to the imposition of Managed Service Plans (MSP) or communication restrictions (including PSSO protocols).
2. Complete audit logs, case notes, and inter-agency data-sharing records (specifically referencing interactions under officer identifiers such as [identifier omitted] and case tracking files).
3. All records, file notes, and system logs concerning review invitations, status flags (including affirmative/negative logging discrepancies), and debt recovery/clawback actions (specifically including Rent Assistance adjustments).
4. Records detailing processing costs, correspondence routing systems, and decision-making matrices utilized across agency silos.

Please acknowledge receipt of this request within the statutory timeframe and provide access to the requested documentation in accordance with the Act.

18. 23:27 AEDT · FEAR AND LOATHING ON THE LEX TRAIL — FORMAL FOI SUPPLEMENT | MSP [identifier omitted], CONTACT ALERTS AND THE DECISION AUDIT

Dear Freedom of Information officers, decision-makers, oversight bodies, parliamentary offices and other recipients,

RE: CONSOLIDATED FOI SUPPLEMENT AND EVIDENCE NOTICE — ORIGINAL RECORDS, PROVENANCE, RESTRICTIONS AND CORRECTION [Applicant details omitted.] Existing matters: Services Australia LEX 93986; LEX 95192; related LEX 95430 / LEX 95433 (statuses to be confirmed); MSP [identifier omitted]; NDIA FOI 26/27-0675 Part 3, case [identifier omitted] ([identifier omitted]). Tracking reference: TS-FOI-061126-B Relevant period: 1 January 2024 to 6 November 2026, except where a specific event is named.

The computer does not have to be sinister to be consequential. An email is received. Someone classifies it. A referral is entered. A contact restriction is recorded. A note appears in another agency's system. Years later, the citizen requests the records and finds that the machinery has documented much of its own work.

That is the question here: WHO DID WHAT, WHEN, USING WHICH RECORD, AND UNDER WHAT AUTHORITY?

I sent a formal four-category FOI request on 6 November 2026 to Commonwealth agencies. This is a more precise supplement to that correspondence and the existing LEX matters. Please link overlapping material to an existing file wherever lawful and practical. I am not requesting unnecessary duplicate searches or that a recipient search another agency's records.

THE SIX DOCUMENTED ANCHORS

1. THE FOI-TEAM REFERRAL: Services Australia's April 2025 Managed Service Plan review in LEX 93986 records a “direct referral from FOI team (excessive correspondence)” to Personalised Services. The record also refers to alleged inappropriate or threatening correspondence; the validity of an FOI application and the content of a particular communication must be assessed as distinct issues.

2. RESTRICTIONS AND REPLICATION: A 24 April 2025 servicing note says “Restrictions replicated in Medicare” (LEX 93986, printed page 23). The released bundle identifies current MSP [identifier omitted], with full face-to-face and partial telephone restrictions scheduled through 19 April 2027. Which particular fields were copied, and when?

3. AN UNFINISHED CONVERSATION: The August 2026 review records “Customer invited to participate in the review: Yes” and “Customer spoken to about the review: No” (LEX 93986, printed page 5). An invitation is not the same thing as an actual conversation, nor does that entry alone establish that no opportunity to respond was provided. Produce the invitation, any response and the assessment of that response.

4. AI ASSISTANCE AND THE LABEL: The 11 August 2026 rationale describes my AI-assisted correspondence as “non-sensical”. That is the agency's description, not a tested conclusion. Which original communications supported the assessment? Was it a human judgement, assisted by an automated tool, or copied from another source? The use of AI to draft an application does not itself determine its validity.

5. THE NDIA NOTE: NDIA FOI 26/27-0675 Part 3, printed page 197, records officer [identifier omitted]'s entry of 19 August 2026, case [identifier omitted]. It contains a “Contact alert” about numerous emails and apparent AI use, and states that Services Australia access was restricted “due to too many FOI requests”. This proves those words were entered in an NDIA case note. It does not yet prove automatic cross-agency transmission, agreement on the underlying facts, or a lawful or unlawful disclosure. The provenance remains the issue.

6. THE WELFARE CHECK AND FINANCIAL CONSEQUENCES: LEX 93986 records incident [identifier omitted] (27 May 2025), including a social-worker recommendation and police welfare-check job [identifier omitted]. The initiating email contained statements of distress relevant to the safety assessment. Separately, I dispute a $2,840.61 Rent Assistance debt and request its calculation and review history. Neither issue should be settled through a shorthand label rather than the underlying evidence.

THE DOCUMENTS REQUESTED — EXISTING RECORDS ONLY

A. REFERRAL AND CLASSIFICATION: Original FOI-to-Personalised Services referral, creation metadata, author, approvals, attachments, classification criteria, records separating formal FOI applications from complaints or other correspondence, and the resulting case-management decisions.

B. INTAKE, REDIRECTION AND HUMAN OVERSIGHT: Existing records or policies showing which mailboxes, correspondence-management systems, filters, routing tools, summarisation or AI-assisted classification functions were actually used for my correspondence. Identify any documented involvement of Microsoft 365, Azure, Genesys or other platforms, without presuming their use. High-level architecture, policy and audit records are sufficient; no credentials, access tokens, protective security thresholds or vulnerabilities are requested.

C. RESTRICTION HISTORY: MSP initiation, amendments and extensions, including the relationship among historical MSP numbers and current MSP [identifier omitted]; notices, incident source records, delegate approvals, reviews, disability-related communication adjustments and less restrictive alternatives considered.

D. CROSS-AGENCY PROVENANCE AND ACCURACY: The source, creation history and audit records for the NDIA [identifier omitted] note and any Services Australia information disclosed to the NDIA. For the Medicare replication, provide field descriptions, date, purpose, authorisation and correction pathway. Identify any records permitting an inaccurate or incomplete notation to be corrected or annotated.

E. WELFARE REFERRAL: Records of the 27 May 2025 welfare-check referral, the risk assessment, the material conveyed to police, the address discrepancy recorded in the note, any subsequent correction, and any review of the decision. A welfare response must be evaluated in its actual safety context; it is not, by itself, a response to an outstanding FOI application.

F. FINANCIAL AND PROCESSING ACCOUNTABILITY: Documents supporting the $2,840.61 Rent Assistance calculation, effective periods, notices, review and correspondence history. Separately, provide any existing staff-time, resource or cost records for LEX 93986 and related FOI work, distinguishing FOI decisions from MSP administration and complaint handling. Do not manufacture a total where no itemised accounting exists.

G. REQUEST REGISTER AND DEADLINES: Existing status and activity histories for LEX 93986, LEX 95192, LEX 95430 and LEX 95433, so far as held by each recipient. Identify valid-request dates, acknowledgements, consultations, extensions, decisions, outstanding work and review rights. Please state where a file remains pending; do not call it a released file merely because a reference number exists.

I request access to the existing responsive documents under the Commonwealth Freedom of Information Act 1982 where it applies. For Victorian or Queensland recipients, please handle this under your applicable access regime, or advise any form, identity, fee or scope requirements needed for a valid application. Private organisations copied are asked only to review records within their remit under their own privacy and complaint processes. Parliamentary and oversight offices are copied for awareness and assessment, not instructed to register FOI requests unless they are the relevant holder.

Commonwealth agencies should acknowledge valid FOI requests within 14 days and ordinarily notify a decision within 30 days, subject to statutory extensions. Please do not mistake my request for a prompt reply or a file-status update for an assertion that every copied body has the same deadline.

If a practical refusal reason is being considered, identify the specific search or decision-making burden and consult about a realistic narrowing. Please distinguish a lawful high-volume FOI strategy from any particular allegation about inappropriate or threatening communications; neither should be proved or disproved simply by labelling a correspondent.

To Senator Malcolm Roberts, Senator Pauline Hanson and oversight recipients: these are testable documentary questions. A contested case note is not a judicial finding; a timestamp is not proof of an algorithm; and a possible disclosure is not a proved unlawful data pipeline. The original records should resolve what can be resolved. [Personal support details omitted.]

The agencies already have the letters. Now I ask for the decision trail.

A label is not the evidence. A checkbox is not a hearing. A copied case note is not an explanation. And a statutory right does not vanish simply because a correspondence-management system finds it inconvenient.

Please preserve tracking reference TS-FOI-061126-B, acknowledge where a valid request has been received, identify the correct file owner, and provide a clear and document-based response.

19. 23:31 AEDT · FEAR AND LOATHING ON THE LEX TRAIL — FORMAL FOI SUPPLEMENT | MSP [identifier omitted], CONTACT ALERTS AND THE DECISION AUDIT

Repeat of letter 18 above (same public text).

20. 01:05 AEDT · FEAR AND LOATHING ON THE LEX TRAIL — FORMAL FOI SUPPLEMENT | MSP [identifier omitted], CONTACT ALERTS AND THE DECISION AUDIT

Repeat of letter 18 above (same public text).

Earlier that night · The twenty documentary requests

At 9:40 pm on 6 November, an earlier letter set out the following scope. These twenty categories were requested in one email.

The original FOI-team referral to Personalised Services, including its date, author, reasons and attachments.
Any assessment distinguishing lawful FOI applications from correspondence considered abusive or threatening.
The original February 2025 Managed Service Plan establishment records.
The source documents underlying the March–April 2025 incident allegations.
The 23 April 2025 recommendation and approval escalating the servicing restrictions.
Records of notices issued to me concerning the original restrictions.
The August 2025 MSP review and supporting evidence.
The August 2026 MSP extension recommendation and approval records not already released.
The source evidence for describing my AI-assisted correspondence as "non-sensical".
The message inventory underlying the count of more than 270 emails.
Documents authorising or implementing email redirection.
Records identifying when FOI correspondence was copied into Personalised Services case notes.
Records determining whether FOI requests or complaints were classified as behavioural incidents.
Records documenting the replication of MSP restrictions into Medicare.
Records of any disclosure of my MSP status or FOI history to the NDIA.
Records supporting, reviewing or correcting classifications concerning my identity and accommodation circumstances.
Assessments of disability-related communication adjustments and procedural fairness during MSP reviews.
Documents concerning any application for a vexatious-applicant declaration under section 89K of the FOI Act.
Existing processing-time, resource and cost records for LEX 93986.
Records showing whether my correspondence was classified as bot-generated, automated or foreign-origin, and the evidence relied upon.

Search This Blog

Yes