cd /news/artificial-intelligence/the-ai-prompt-a-canadian-mla-read-ou… · home topics artificial-intelligence article
[ARTICLE · art-73374] src=dev.to ↗ pub= topic=artificial-intelligence verified=true sentiment=· neutral

The AI Prompt a Canadian MLA Read Out Loud — And What It Teaches

A Canadian legislator in New Brunswick read an AI prompt aloud during a floor speech, including the chatbot's meta-commentary. The incident highlights the importance of reviewing AI-generated text before use, as the tool did not fail but the human review step did.

read4 min views1 publishedJul 25, 2026

A Canadian legislator read an AI prompt out loud in a floor speech, and the clip is doing the rounds this week for all the wrong reasons. According to Ars Technica, Bill Oliver, a Progressive Conservative MLA in the New Brunswick legislature, said "Public confidence in the office of an advocate matters," and then kept reading: "Here's a more natural, flowing version of that section that reads like a legislative speech rather than a series of short points."

That second sentence was never meant to be spoken. It's the chatbot talking to the human. He read it anyway, reportedly without blinking.

I'm not writing this to laugh at a politician. I'm writing it because the exact same mistake is one keystroke away for every student, freelancer, and small-team builder in Sri Lanka who now drafts with an LLM. The interesting question isn't "was AI used." It's "who was supposed to read this before it went out, and why didn't they."

The model did its job. It rewrote a bullet-point section into flowing prose and prefixed the result with a one-line note explaining what it did. That prefix is standard chatbot behaviour. The failure was entirely on the human side of the handoff:

Key takeaway:The tool didn't fail. The review step failed. An LLM will hand you a draft with scaffolding still attached — the "here's a version that…" line, a stray"Let me know if you'd like…", a placeholder in square brackets. Deleting that scaffolding is your job, not the model's.

Every one of those three steps is something you control. None of them requires trusting the AI more or less. They require reading your own output before you ship it.

LLM output has a recognisable residue. If you draft with a chatbot, learn to spot these before the text leaves your machine. Here's the common giveaways and the fix:

Tell What it looks like Fix
Meta-commentary "Here's a more natural version of…" Delete the whole framing line
Sign-off bait "Let me know if you'd like me to expand" Delete; it's talking to you
Placeholders
[Insert company name] , [date]
Search for [ and fill or cut
Hedge stacking "It's important to note that…" x5 Cut the throat-clearing
Filler adjectives overuse of "seamless", "cutting-edge" Replace with specifics or delete

The reliable move is mechanical: after the model gives you text, run a find for [

, for "here's", for "version of", and for "let me know". Thirty seconds. It would have caught the New Brunswick speech instantly.

If you write in Sinhala or Tamil and translate through a model, the residue often survives translation too, so the same check applies to both languages. The correct mental model is that the LLM is a fast junior who writes an okay first draft and never checks their work. You would never forward a junior's draft to a client untouched. Same rule here.

I lean on AI to reshape messy paragraphs constantly, and I still read the whole thing back before it goes anywhere near a reader. If you want a second machine opinion on whether your text reads as obviously AI-generated, our AI content detector comparison lines up how the popular detectors score the same passage — useful for a gut check, though no detector is a substitute for reading it yourself. And if the problem is the opposite — a wall of chatbot text you need to shrink — the AI text summarizer will do that in the browser without an account.

If you're a UCSC student submitting coursework, a freelancer sending a Colombo client a proposal, or a two-person startup writing your first landing page, you don't have a comms department to catch a slip like this. You are the review step. There is no editor between your draft and the world. The higher the stakes and the smaller the team, the more the final read-through is non-negotiable. A legislature has Hansard transcripts, opposition MLAs, and a national press watching. Your client just quietly decides you're careless and doesn't reply.

The good news: the fix costs nothing and needs no tooling. A free-tier chatbot plus your own eyes beats a paid one used carelessly, every time. The skill that's scarce now isn't prompting. It's the discipline to read what came back.

The New Brunswick clip is funny for a day and forgotten by next week. The pattern behind it is going to keep happening as more people draft with AI and skip the read-back. Don't be the case study.

Three habits, starting today:

[

, "here's", "version of", "let me know" before anything ships.The tools are good enough that the only remaining variable is you. That MLA had a working AI assistant and a broken review habit. Keep the assistant. Fix the habit.

── more in #artificial-intelligence 4 stories · sorted by recency
── more on @bill oliver 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/the-ai-prompt-a-cana…] indexed:0 read:4min 2026-07-25 ·