Weaponized Clarification: How LAC Obstructed a Privacy Act Request Through Contradiction, Misquoting Law, and Strategic Delay

I. Introduction: A Clerical Farce with National Implications

There is a specific kind of Canadian scandal—quiet, paper-based, deniable. It does not involve suitcases of cash or rogue billionaires. It begins with a PDF.

On April 4, 2025, Kevin J.S. Duska Jr., a Calgary-based privacy researcher and founder of the private intelligence firm Prime Rogue Inc., received a routine email from Library and Archives Canada (LAC). It included a boilerplate clarification letter regarding a Privacy Act request he had submitted weeks earlier on March 26—one of over 120 such requests fulfilled across federal departments as part of a systemic transparency audit known internally as Echo12b.

The request was unremarkable: a standard s.12(1)(b) submission under the Privacy Act, seeking all personal information about the requester held by LAC, including internal mentions, ATIP notes, access logs, and metadata spanning forty years. The language had been vetted by legal counsel, tested across dozens of departments, and accepted—without issue—by nearly every institution contacted.

Except LAC – and the Canadian Nuclear Safety Commission – but we don’t want to get into the dark timeline twice in a single piece.

What followed was not a denial, exactly. It was something stranger. A slow, recursive procedural spiral in which LAC staff insisted that the request was unclear, that it changed over time, that it lacked specificity, and, most notably, that the requester had a “legal obligation” to clarify it—a phrase that would come to define the dispute.

In response, Duska offered clarifications. Then reiterations of clarifications. Then clarifications of clarifications. He provided plain-language summaries, legal citations, operational guidance, and even suggested that perhaps the “legal obligation” claim was a translation error—a generous exit strategy for an institution that had, at that point, already begun to unravel its own justifications.

Instead, the office doubled down. The phrase was not a mistake. The delay was not a misunderstanding. And the request, they insisted, was simply too broad to process—even as they quoted it back, word-for-word, as accurate.

“It stopped being administrative failure,” Duska told us in an interview this week. “It became performance. Their position wasn’t procedural. It was theatrical. I felt like I was being scolded by an underqualified school principal on their first day of work.”

This article is not about a privacy request. It is about what happens when the guardians of information weaponize ambiguity, and when the process of access becomes a deterrent in itself. It is about fear of metadata. It is about narrative control.

And it is about a federally funded memory institution that, when asked to remember, chose instead to redact its own reflection.

II. The Request That Didn’t Change

At the core of this confrontation lies a bureaucratic fiction: that the request was somehow unstable, shifting, or evolving over time. In reality, the wording has remained functionally identical since April 4, 2025—the same date LAC first asked for clarification.

The request read:

“I am requesting access to all personal information under the control of Library and Archives Canada that references or pertains to me—under any of the following name variants: Kevin Duska, Kevin Duska Jr., or Kevin J.S. Duska Jr.—from January 17, 1985 to present.
This includes but is not limited to: internal communications, access logs, audit trails, metadata fields, correspondence referencing me (internal or interdepartmental), ATIP processing notes, triage memos, and any operational or archival records where my name appears in relation to LAC holdings, systems, or ATIP activity.
This request is filed under section 12(1)(b) of the Privacy Act and includes both operational and archival holdings.”

This language has now been quoted back to Duska by LAC itself—confirmed, endorsed, and yet paradoxically described as too broad to process. The problem, then, was never the wording. It was that the wording worked—too well, perhaps, for an institution unprepared to confront its own metadata footprint.

“As you can see, they told me I kept changing the request,” Duska said. “But every version they objected to was a version they themselves quoted as final. That’s not confusion. That’s a tactic. It seems like their default approach is to attempt to ‘wear down’ the requester through amateurish circular argumentation filled with fallacies – the efforts have been so pathetic they’ve made me laugh. Honestly, if I’m to intellectualize it, it feels like a very pathetic example of institutional DARVO (Deny, Attack, Reverse Victim and Offender) except the abuse is bureaucratic.”

Each time LAC insisted the request was unclear, Duska responded with increasingly precise documentation. He clarified that he was not seeking a document-by-document review of archival holdings. He clarified the operational-archival distinction. He offered a detailed guide on how LAC could conduct metadata-indexed searches using standard archival tools. He clarified that his request, like all Echo12b filings, was scoped to avoid unreasonable administrative burden.

At no point did LAC identify a single specific ambiguity in the request. They simply asserted one existed.

“If they had said: ‘We don’t have the ability to search these systems’—that would be fine,” Duska said. “Instead they tried to reframe the request as unreasonable while simultaneously quoting it back as accurate. It’s a contradiction pretending to be policy. It’s Kafkaesque!”

This was not the first time a federal institution attempted to shake the frame. But few did it so overtly—and fewer still while admitting that responsive records likely existed.

That’s where the narrative began to wobble. And that’s where the phrase—“you have a legal obligation to clarify”—entered the stage.

III. Legal Obligation: A Statement So Nice They Said It Twice

On April 22, 2025, Maryse Pelletier, Senior Analyst at Library and Archives Canada’s ATIP and Litigation Branch, issued a statement so bureaucratically brazen it has now been canonized in two formal complaints:

“You have a legal obligation to provide further clarification…”

It wasn’t qualified. It wasn’t hedged. It was used to justify placing a lawful Privacy Act request on hold. And it was, unequivocally, false—both in law and in practice.

Kevin Duska responded immediately, citing section 12(1)(b) of the Privacy Act, the Directive on Personal Information Requests, and related jurisprudence confirming that the duty to assist lies with institutions—not individuals. He even extended an institutional lifeline: suggesting, magnanimously, that the phrase “legal obligation” might have been the result of an innocent translation error from French.

LAC declined to take it.

Instead, the file was redirected—not to LAC’s lead ATIP official, Lesley Bilton-Bravo, who had been copied on all correspondence since—but to Geoffrey Keelan, Deputy Director of the Complaints Management Team, ATIP Branch. In effect, the office sent a potential complaint file to the office responsible for complaint oversight.

Keelan’s intervention was immediate. He emailed Duska claiming that the request itself had not been called contradictory—only Duska’s response. He further insisted that the ongoing confusion was impeding assistance, and proposed a phone call to clarify.

The effect was pure recursion: the man responsible for managing complaints was now actively producing one, while suggesting the complaint was a tone issue.

“They could have said: ‘We misspoke.’ They could have blamed translation. Instead, it seems like they turned the gaslight up a notch and hoped I’d lose track of my own syntax.” —Kevin Duska

Keelan’s title bears repeating: Deputy Director, Complaints Management Team, ATIP Branch. Which is to say: a senior official responsible for ensuring lawful institutional responses to federal access requests was now implicated in perpetuating the very conduct the complaint process exists to address.

This is no longer a question of misunderstanding. It is the institutional weaponization of misinterpretation—first to paralyze a request, then to deny it ever happened.

Two complaints are now active:

• A Privacy Act complaint under section 29(1) for constructive denial and procedural obstruction;
• A forthcoming Accessible Canada Act complaint for failure to accommodate a documented visual disability (amblyopia), and for erecting systemic access barriers through misapplication of legal duties.

Keelan and Pelletier are now named subjects in both.

But the structural irony is deeper.

In a memory institution tasked with preserving truth and procedural integrity, two senior officials cited imaginary obligations, ignored correction, and rerouted a file into their own management system—all while requesting “clarity” from the person they just misinformed.

“It’s like asking my 6 month puppy Wilco to investigate who stole the ham sandwich off the end table. OMG I need to send you a picture – she started smiling – finally.”

LAC was given multiple chances to walk it back. Instead, it walked in circles—while the statute kept ticking. I am posting the picture of Wilco Duska sent me as this article needs a puppy-oriented therapy break.

So cute! OMG Puppies!!! ¯\_(ツ)_/¯ – and one must thoroughly question whether the people at LAC’s ATIP branch treat puppies with the care they deserve, given how they have treated this request.

IV. If You’ve Already Searched, Then What Are We Clarifying?

By April 23, Library and Archives Canada’s procedural rhetoric reached a point of surreal self-cancellation. In his most recent message, Geoffrey Keelan—acting as both responder and potential complaint subject—wrote the following:

“We can confirm that no records in our archival holdings are responsive to your request.”

This was followed—without irony—by a renewed request for clarification.

“Can you please provide some likely areas where you think records that might pertain to you exist?”

Which begs a very simple question: if a search was conducted and returned a “NIL” result, then what—precisely—is LAC still unclear about?

Either:

1. LAC conducted a search based on the existing request scope and found nothing;
2. Or it did not understand the request and therefore could not have searched in the first place.

You cannot not understand a request and search against it at the same time. Yet this is the core contradiction LAC has now embraced as its internal logic. It is, effectively, asking a requester to clarify the thing it has already processed and responded to.

“It’s like being told the kitchen is empty before you’ve turned on the light. The only reasonable conclusion is that someone didn’t want to find anything.” —Kevin Duska

This contradiction is made more revealing by the structure of LAC’s holdings.

Library and Archives Canada operates one of the most documented metadata hierarchies in the federal government. Its systems—ranging from MIKAN to AIMS to RAD—are designed specifically to allow searchability at file-level, accession-level, and series-level.

The request from Kevin Duska did not ask for manual review. It asked for exactly what the system was designed to do: identify metadata fields where his name (or any variant of it) appeared. These include:

• ATIP routing notes
• Access logs
• Triage memos
• Reproduction service orders
• Interdepartmental correspondence
• Internal communications referencing his name in holdings access or processing

These are standard, retrievable, and within scope—as confirmed by 121 other institutions that accepted the same request without hesitation.

LAC, meanwhile, continues to pretend that the request is both too vague to search and already searched.

“You can’t claim the car won’t start, then argue you’ve already driven it around the block.”

Keelan’s latest message does precisely that. It reaffirms the scope, then blames the scope for the absence of results. It confirms searchability, then denies the logic of searching. It recites the exact wording of the request—then accuses the requester of changing it.

All of this while Lesley Bilton-Bravo, LAC’s ATIP Branch lead, watches silently from the CC line.

The result is not just procedural contradiction. It is intentional opacity—the institutional act of collapsing clarity under the weight of its own misdirection.

In intelligence terms, this is a signal inversion loop: a bureaucratic tactic where comprehension is denied not because the request is unclear, but because clarity is strategically inconvenient.

And so LAC waits—for clarification it has already received, about a search it already conducted, regarding a request it claims not to understand.

It is Kafka with a CC field.

This timeline is so dark that I’m inserting a photo of my dog Murphy to lighten the mood, and preserve my mental health.

V. A “Legal Obligation” That Was Never Real — And a Chance to Walk It Back

On April 22, 2025, Maryse Pelletier of Library and Archives Canada asserted the following in writing:

“You have a legal obligation to provide further clarification as it is unreasonable to ask the entire institution to search their records for your name…”

This phrase—legal obligation—is not simply incorrect. It is an invention. A fabrication dressed up in bureaucratic language, presented as if codified, and leveraged to frame an otherwise valid request as procedurally defective.

The Privacy Act contains no such requirement. The Directive on Personal Information Requests imposes no such duty. Federal case law from Michel v. Canada (AG) to Canada (Information Commissioner) v. Canada (Minister of National Defence) is clear: the legal burden falls on the institution to assist, not the individual to pre-filter internal searches the institution itself is equipped to conduct.

“I almost spat my coffee out – I laughed so damn hard. To assert that I was under a ‘legal obligation’ was not just wrong — it was a claim I believe was made in bad faith, designed to construct a future justification for denial. That said, I could also super easily see it being an error in translation, something like bilingual aphasia, because I’m an English-French Quebecois ‘moitié-moitié’ mutt and I could imagine a less meticulous version of myself making that very same error.” —Kevin Duska

What makes this maneuver especially revealing is what came next.

In a subsequent round of correspondence, when given the opportunity to walk back this misstatement—perhaps as a mistranslation (given Ms. Pelletier’s potential position as a French-speaking analyst)—the institution declined.

“If this was simply a translation issue—where ‘obligation légale’ was used colloquially or imprecisely by a native speaker of French—I would completely understand… and welcome confirmation so this meta-discussion can be set aside.” —Kevin Duska, April 23

No such confirmation ever came.

Instead, the institution pivoted again, this time insisting the issue wasn’t the request, but the tone or context of the response. A procedural misstep became a personal miscommunication. The goal was now to reframe legal misrepresentation as interpersonal confusion—a familiar tactic for institutions seeking to diffuse accountability.

“You misunderstood what I meant,” becomes the shield for, “You correctly understood what I said — and I shouldn’t have said it.”

It is worth pausing here. The Privacy Act is one of the few federal statutes that binds institutions by law to procedural fairness. Misstating its provisions—especially in a way that could deter or delay lawful access—has real legal consequences.

It can trigger:

• A section 29(1) complaint to the Office of the Privacy Commissioner (already submitted),
• A systemic barrier investigation under the Accessible Canada Act,
• Federal litigation and potential human rights tribunal referrals
• And in this case, a public documentation of the error in an open-source oversight audit published by Prime Rogue Inc.

Ms. Pelletier’s statement—absent retraction—now stands as a live artifact of institutional overreach.

And it has already been preserved, indexed, and cited in multiple federal accountability briefings.

It is not just the misapplication of law that matters. It is that the institution was given the chance to correct it, and instead chose to reassert confusion as policy.

Which raises a larger question: If the legal obligation never existed, and the institution knew that, what purpose did the false claim serve?

The answer may be discomforting.

It served the purpose of intimidation—however subtle, however bureaucratic—by framing lawful access as a violation of norms, and lawful insistence as procedural defiance.

That isn’t misunderstanding. That is structural defense. And it’s one half goose-step (a reference to blind procedural discipline, not its most infamous practitioners, unless the boot fits) removed from institutionalized disinformation.

VI. Conflict by Design: When the Complaint Handler Becomes the Problem

On April 23, 2025, a new name entered the conversation: Geoffrey Keelan. Introduced as the Deputy Director, Complaints Management Team, Keelan inserted himself into the handling of a file he was functionally responsible for investigating.

It is difficult to overstate how unusual this is.

The role of the Complaints Management Team—in both name and mandate—is to monitor institutional compliance with access obligations and to identify where errors, obstructions, or procedural irregularities may have occurred. In most federal bodies, such roles are structurally separate from active file processing to preserve basic accountability firewalls.

But at LAC, Mr. Keelan’s involvement did not signal institutional reflection. It signaled institutional entrenchment.

Instead of conducting any neutral review or facilitating resolution, Keelan:

• Reaffirmed the claim that the request was “unclear,” despite having just quoted it verbatim.
• Reframed previous institutional misstatements as misunderstandings, including a line-by-line dispute over whether “errors” applied to the request or the response.
• Repeated the institution’s demand for a “succinct, in your own words” confirmation of already-established facts.
• Introduced further confusion by suggesting that citing relevant legal precedent could somehow alter the legal regime under which the request was filed.

“Several times below your text cited OIC decisions regarding access requests. You have made a privacy request, not an access request… Can you please confirm you would like us to treat this as a privacy request.”

This is not merely off-base. It is procedurally illiterate. The OPC has, for over a decade, confirmed that its findings under the Privacy Act routinely reference ATIP jurisprudence because the two regimes are interpretively aligned. They share procedural obligations, redaction standards, and metadata precedents.

Keelan’s mischaracterization isn’t a lapse in comprehension. It is an administrative gaslight — meant to provoke second-guessing of a process already affirmed by 121 federal institutions.

“We are being asked to trust a purportedly senior official who both adjudicates complaints and inserts himself into the very files that will be reviewed. That isn’t oversight — it’s circular defense. Literally, my mind is blown – well not literally but – you know what I mean. It’s also very difficult to understand the correspondence. I find the writing to be very poor, and it honestly feels like a throwback to grading C- argumentative essays when I was a TA.” — Kevin Duska

This is the heart of the conflict now on record.

Library and Archives Canada has allowed the official tasked with protecting complainants to become the primary barrier to lawful access. That is more than a red flag — it is a systemic vulnerability. It means no distinction exists between handler and obstacle, between facilitator and enforcer.

LAC’s Complaints Management Team is now part of the complaint.

And as a result, both Geoffrey Keelan and Maryse Pelletier have been named in a live section 29(1) complaint to the Privacy Commissioner of Canada — for misapplication of law, procedural intimidation, and the appearance of administrative conflict.

In any other institution, this would prompt an internal escalation.

At Library and Archives Canada, it prompted crickets.

This isn’t just a bad faith exchange. It’s an indictment of how weak Canada’s internal accountability systems are when no one is watching — and how confidently public servants behave when they think no one ever will.

VII. A Reasonable Request, a Manufactured Crisis

By April 24, 2025, it was clear that LAC was not confused. It was strategically performing confusion.

The text of the request had been confirmed, repeated, and acknowledged—verbatim—by Geoffrey Keelan in writing. It had not changed. No amendment had been made. Clarifications had only been provided to address invented ambiguities raised by LAC staff themselves. Despite this, Keelan insisted the request had been altered multiple times, and warned that “generating new text” made it difficult to determine what to process.

This would be comical if it weren’t part of a federally mandated rights process. The gaslighting wasn’t even coherent.

Let’s be precise:

• The request text was consistent from Day One and reaffirmed repeatedly.
• Keelan himself quoted it accurately in full.
• LAC’s archival and operational distinction had been preemptively addressed and acknowledged.
• The accessibility request had been properly cited under the Accessible Canada Act, Canadian Human Rights Act, and Treasury Board standards.
• Known interactions with LAC (ATIP, Reprography, metadata indexing) were transparently referenced to assist the search.
• Legal precedent (including OPC rulings and SCC decisions) was cited to reinforce—not confuse—the scope.

At every stage, LAC’s response strategy relied on a bureaucratic performance of helplessness: “We just don’t know what you want,” said the institution that handles information for the entire country. “If only we had clarity,” said the people ignoring the paragraph they had just confirmed.

And when pressed, LAC doubled down. The request, they argued, was too broad. “It would require every LAC employee to search every record,” Keelan wrote—an assertion so theatrically disingenuous it might be mistaken for satire.

No one asked for that.

The request seeks metadata-indexed, file-level, or accession-level references to the requester’s name. This is a standard query, processed routinely across federal institutions. Keyword searches in email archives, log systems, and archival indexes are not esoteric tools—they are part of LAC’s job. They are part of their software. They are why LAC exists.

And yet, LAC insisted that unless the request could name which employee interacted with the records—or divine their future location—it would not proceed.

This isn’t a misunderstanding. It’s fabricated administrative impossibility. It’s Kafka by design.

“They kept demanding I confirm what they already quoted, re-explain what I’d clarified three times, and justify a search methodology I explicitly limited to file-level and metadata. It was like arguing with an institution that knew it was wrong and had already written the script for pretending it wasn’t. Moreover,. I felt that he [Keelan] was very adversarial. It’s almost like he thought the institution’s honour was being defiled by my request, I thought. Paradoxically, I also felt that I was engaged in an argument with a toddler.” — Kevin Duska

The most generous interpretation is that LAC has constructed an internal doctrine of “clarification” so absurdly recursive it collapses under its own inertia. The more plausible explanation is simpler: this is institutional risk avoidance, masquerading as due process. A civil service trained to see access as exposure rather than duty.

The real crisis here is not a requester’s “vague” wording. It’s that Library and Archives Canada cannot—or will not—handle a straightforward Privacy Act request without entering a posture of hostile retreat.

And that posture now carries consequences.

VIII. Conflict of Interest by Obstruction

By April 24, Prime Rogue Inc. formally notified Library and Archives Canada that both Geoffrey Keelan and Maryse Pelletier were now named subjects in an active Privacy Act complaint under section 29(1), citing procedural obstruction, misapplication of legal authority, and the introduction of false or misleading information that risked chilling access rights under federal law.

Let’s be direct: the issue isn’t just delay.

It’s the sustained pattern of conduct from LAC’s ATIP personnel, and in particular from Mr. Keelan—whose job title, curiously, is Deputy Director of the Complaints Management Team. That’s right: the official actively impeding the file is the same official nominally responsible for safeguarding due process when a complaint is lodged.

It would be difficult to script a more obvious structural conflict.

Keelan’s interventions were not just bureaucratically unhelpful—they were legally destabilizing. His insistence that the requester had a “legal obligation” to further narrow scope (later walked back by performance of confusion), his invocation of a court case (Leahy) that did not support his argument, and his repeated mischaracterizations of the request all point toward something deeper than incompetence.

They reveal an official who is no longer acting as a neutral facilitator, but rather as an institutional risk actor attempting to suppress retrieval by shifting burden, obfuscating clarity, and strategically stalling under the guise of assistance.

That alone constitutes a breach of LAC’s obligations under the Directive on Personal Information Requests. But combined with his formal mandate as Deputy Director of Complaint Management, it creates what legal scholars and information rights advocates refer to as reasonable apprehension of bias.

Worse, this obstruction happened after multiple procedural lifelines were offered:

• Pelletier’s “legal obligation” line was given the chance to be walked back as a translation error—an offer never taken.
• Keelan was given a full plain-language summary of how LAC could locate responsive records using standard tools and indexes.
• The scope was re-confirmed—verbatim—by Keelan himself.
• The accessibility accommodation was documented, justified, and re-acknowledged.
• Repeated chances were given to proceed without prejudice.

LAC chose instead to fabricate narrative inconsistency where none existed, then blamed the requester for introducing “changes” that were already confirmed as consistent.

“I don’t know if it’s obstruction or performance art. But it’s not compliance. My wife has been an archivist for, like, 15 years, I think, and she referred to this as ‘institutional misconduct’ and ‘individual incompetence.’ Having myself done archival research since I started my PhD in 2007, given that I’m literally a qualitative IR scholar, I find this more dystopian than bringing vodka to the archives in Moscow so they’d let me see a file I was allowed to see anyway.” — Kevin Duska

At a certain point, denial becomes systemic. And when that denial flows from officials whose role is to manage complaints, not trigger them, the line between conflict and liability begins to blur.

By naming both Keelan and Pelletier as subjects in the complaint, Prime Rogue Inc. is not making a rhetorical statement—it is asserting a procedural necessity. The individuals now involved cannot be expected to impartially administer a file they’ve spent weeks mischaracterizing, delaying, and strategically undermining.

That conflict now forms part of a broader record—and that record, in turn, will form the backbone of a second wave of oversight.

Because while access rights are individual, accountability is institutional. And LAC has now exposed itself on both fronts.

IX. Silence as Strategy, Delay as Denial

If Geoffrey Keelan’s emails read like bureaucratic abstraction layered over performance-grade fog, they’re working exactly as intended.

What LAC has executed here is not an accidental failure to process a request. It is a calibrated attempt to neutralize a procedurally valid Privacy Act inquiry through manufactured confusion, weaponized delay, and reflexive deference to internal incapacity.

Every tactic fits a now-familiar institutional pattern:

• Recharacterize the request as unclear, despite verbatim repetition and internal acknowledgment of its specificity.
• Invoke legal standards inaccurately—in this case, citing Leahy v. Canada (CIC) while omitting that the Leahy request lacked prior interactions, a timeframe, or meaningful identifiers.
• Ignore OPC precedent confirming that ATIP processing notes, internal triage, and metadata constitute disclosable personal information under s.12(1)(b).
• Frame clarification as instability, even when the exact same scope was quoted, confirmed, and then treated as suspect.
• Propose a phone call—a classic obfuscation move that strips the request of auditability and moves the interaction off-record.
• Threaten abandonment despite the file being legally complete and procedurally sound.

This is not passive misunderstanding. It is active misdirection.

And behind it lies a deeper logic: if the file can be looped, stalled, or buried long enough, the incentive to pursue it collapses. Institutional memory fades. Procedural inertia takes over. The appearance of progress substitutes for the act of compliance.

That’s not just delay. It’s a constructive denial—a term used by the Office of the Privacy Commissioner when an institution frustrates access rights through improper deferrals, administrative inaction, or procedural double-speak.

LAC is not simply slow. It is misusing process as a defense against transparency. It is stalling under the guise of assistance—a tactic so common it’s become a hallmark of fragile federal compliance regimes.

What’s especially revealing is that no one at LAC has outright refused to process the request. That would be appealable. That would be clear.

Instead, they strategically defer clarity, then accuse the requester of confusion.

“This isn’t about searchability. It’s about plausible deniability wrapped in polite dysfunction. When myself and Andrej [Prime Rogue Inc counsel] finalized the text of the initial request, we knew that there would be follow-ups. Given that we’re attempting to gather as much qualitative data as possible, the follow-up method, and response to case law, is itself part of the Echo12b project. Admittedly, I tried to make myself look like a rube when framing because I felt like that would elicit a truer response. Clearly, when dealing with LAC, that’s what I got.” — Kevin Duska

The endgame is chillingly effective: the file never moves forward, but neither is it closed. The record is neither accepted nor denied. The access right remains technically intact, but functionally suspended.

This is what happens when federal institutions realize that slow is safer than saying no.

And that’s exactly what LAC has done.

X. Silence as a Service

There is a point in every institutional dispute where language stops performing clarity and begins performing control. With Library and Archives Canada, that threshold was crossed when it invented a “legal obligation” where none existed, misapplied a Federal Court ruling to its own acknowledged record holders, and then attempted to walk back both errors by insisting it had been misunderstood.

The result is not just misdirection — it’s procedural performance.

The clarity of the request was never in question. Its scope never changed. The only variable was LAC’s tolerance for what it implied: that a federal institution, tasked with memory stewardship and democratic recordkeeping, might be required to acknowledge a paper trail that already exists.

And that, in the end, is the core discomfort.

Because once it is admitted that a name like “Kevin J.S. Duska Jr.” — attached to a private intelligence firm conducting a national access audit — might be scattered through access logs, triage memos, referral chains, or access-related metadata, the next question becomes: what else have they already seen? And what institutional assumptions are suddenly in the open?

Rather than answer that question, LAC has chosen to destabilize the request, reposition the law, and, when cornered, question the tone of the correspondence — as if confidence were the offense, and not the denial itself.

This is how systems process dissent without processing records: they delay, reframe, and push the conversation into abstraction. They pretend clarification is escalation. They convert statutory rights into staff workload. They equate audit with disruption.

The danger isn’t just that this request was delayed. It’s that the response was built on silence disguised as structure.

But silence, in this case, is not neutral. It is tactical. It performs one thing while concealing another.

And the moment it is broken — by complaint, by article, or by public documentation — the choreography collapses.

LAC had multiple opportunities to walk back the “legal obligation” as a translation error. It had opportunities to engage the clarification constructively. It had the chance to treat the request as valid, lawful, and unexceptional — because it was all of those things.

It chose instead to escalate confusion into consequence.

That choice now has a record.

Epilogue: Institutional Theatre

In a government building in Gatineau, a senior analyst misquoted federal law. A deputy director confused clarification with contradiction. And somewhere along the way, a public access request became a bureaucratic morality play — complete with a cast, script revisions, and offstage whispers about tone.

What started as a standard Privacy Act filing has become a procedural psychodrama about what it means to be searchable, knowable, and logged.

Library and Archives Canada is not a villain in this story. It is something more complex, and far more Canadian: a character actor in its own myth of neutrality. A memory institution performing uncertainty about how memory works. A federally mandated archive that recoils from the notion it might remember anything at all.

And so the curtains fall, not with resolution, but with what bureaucrats call “continued correspondence.” The file is still open. The record is still being assembled. And the institution — caught between its mandate and its habits — is left improvising clarity one redacted line at a time.

After all, this isn’t really about one request. It’s about what happens when a public-facing institution is asked to face the public — and can’t.

In theatre, we call that breaking the fourth wall.

In government, we call it compliance.

Wilco is still smiling. Murphy is still skeptical. And somewhere in Gatineau, a metadata audit is still on hold.