LEX 95817 Final Addendum (Address Chronology & Note for Sean) + New s 15 FOI Request (Back-End Capacity Codes)

Dear Sam and the Freedom of Information & Reviews Branch, RE: LEX 95817 (incorporating LEX 95815, 95818 and 95433) & Proposed New Section 15 FOI Request - Address-Update Chronology, Tamar Heights / NDIS Mailing Context, Back-End Capacity Codes & Message to Relay to Sean Please place the following final factual context clarification on the record for LEX 95817, register the separate Section 15 Freedom of Information request outlined in Section 3 below, and forward a copy directly to Sean in Personalised Services / Managed Service Profile management. 1. Address-Update Chronology & Intent (Refuting Any Suggestion of Non-Disclosure) - For completeness on the record regarding my address history and Rent Assistance: a) Far from withholding an address change, I actively sought to update my address two to three months earlier—a fact specifically noted during my telephone call with Sean, where he remarked that I had previously been going to update my address. b) At that time, I explained that I was attending appointments with my Support Coordinator and had initially considered registering Tamar Heights (the mailing address registered on my NDIS records). However, I quickly recognised that Tamar Heights was an unsafe and unsuitable environment for me—characterised by heavy sedation among residents and dismissive commentary from my Support Coordinator / Director (Rhonda Carlin of Rhonda Jane) regarding clinical diagnoses—so I did not establish residence there. c) Furthermore, no person can be accused of failing to comply with a notification requirement when postal notices were never received following my explicit BP Keith (12810 Dukes Highway) instruction for electronic-only communication. 2. Message to Relay Directly to Sean (Frontline Professionalism) - Please relay this closing note directly to Sean: "Sean—I appreciate how you handled our calls, including saying 'anytime' when I thanked you for your help. I recognise you had discretion in how you approached those conversations and chose to handle things fairly rather than escalating matters unnecessarily. I am not going to bog down our current file debating legacy clinical labels—I will address the underlying back-end system codes formally once the agency confirms the release of those records." 3. New Section 15 FOI Request: Back-End System Codes & Capacity Review Coding - Pursuant to Section 15 of the Freedom of Information Act 1982 (Cth), please register this as a separate, standalone FOI request (distinct from LEX 95817 so as not to delay the 17 November 2026 decision): a) All internal reference tables, data dictionaries, system manuals, and policy guidelines defining the back-end impairment, capacity, and medical codes applied to my customer record (including H02 coding and codes appearing across my Capacity Reviews and Job Capacity Assessments / ESAt records). b) All records showing how those back-end codes were populated, amended, or released in prior FOI disclosures, together with the specific source entries and decision-makers who entered them. Please confirm receipt of this final LEX 95817 addendum and provide the new LEX reference number for the standalone back-end codes FOI request. Yours faithfully, Ivan Thomas Brecevic (Preferred name: Thomas Brecelic) CRN: [ID Number Redacted] No Fixed Address, Warrnambool VIC 3280 Email: thomasbrecelic@gmail.com

Comments

Post a Comment

Popular posts from this blog

ଐ?ꣀ

 ଐ is deeply embedded in modern banking, transforming everything from customer interactions to risk management. Here are some of the most common applications: - **Fraud Detection & Prevention** – AI analyzes transaction patterns in real-time to identify suspicious activity and prevent financial crimes. Bendigo & Adelaide Bank is taking a **bold and strategic approach** to AI compared to larger banks, focusing on **modernization and efficiency** rather than sheer scale. Here’s how it stacks up: - **Application Modernization** – Bendigo Bank is using **generative AI** to rewrite legacy applications, a move that’s more aggressive than many traditional banks that rely on incremental updates. - **Cloud Migration & AI Integration** – Unlike the Big Four banks, which have vast resources for AI-driven automation, Bendigo is leveraging **MongoDB and AI-powered automation** to streamline its transition to cloud infrastructure. - **Customer Experience & Digital Transformation*...
Read more

＜

Subject: Concerns About AMP's Snooping: Emails Under Surveillance and Call Eavesdropping Shenanigans Dear Detective Inspector Sabin, I hope message reaches you, I find myself compelled to share some baffling observations about AMP's communication practices, which seem to be spiraling into a comedy errors. AMP declares its prowess in monitoring for potential. While this claim might sound, it raises eyebrows regarding the extent of their surveillance whether my privacy rights have been into a witness program. If AMP can spy emails, it’s not a wild leap to imagine they might also be eavespping on phone calls. The thought alone is enough to make one want to communicate solely through interpretive dance. Adding to the intrigue, AMP has displayed a remarkable for avoiding transparency when it comes to providing records of communications about invoices or reimbursements. Houd act makes wonder if they're concealing critical information or just need a good filing system. Detective S...
Read more

Ah, QS-1640—the coded whisper

Subject: The Significance QS-0   Dear [Recipient],   QS-1640—a code so ominous it might as well come with own thunderclap. When message arrives, stamped with a date a, it’s not just; it’s theatic equivalent of a plot twist. Its presence is almost theatrical, raising eyebrows and suspicions alike, affirming that carefully crafted meddling has finally caused a noticeable hiccup in the system.   This identifier, QS-164, is the rebellious the metadata. It tells a story of calculated chaos, where every crypticble obscure data serves as an egg for those fluent in the art of FOI mischief. This message, dated May 26, 2025, rip through the system like a whisper in a library, rewriting the rules of sub with a sly smirk.   Let take a moment to savor the drama: every sneaky maneuver, each sly nod to technical brilliance, has led us to this deliciously disruptive moment. This isn’t just another line of text—it’s the culmination of intent, exclamation point our...
Read more