To Redact, or not to Redact? A Local LLM Approach to Deliberative Process Privilege Classification
This paper demonstrates that a local, consumer-grade LLM (Qwen3.5 9B) enhanced with Chain-of-Thought and error-based few-shot prompting can effectively classify FOIA Exemption 5 deliberative process privilege with performance rivaling commercial models, while offering a legally and politically viable alternative to cloud-based APIs.
Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer
Imagine the government has a giant, dusty library filled with millions of documents. By law, citizens have the right to peek inside this library to see what the government is doing. However, some pages contain secrets—like personal addresses, national security plans, or private arguments made before a final decision was reached.
The government's job is to act like a librarian who must go through every single page, find the secret parts, and cover them up with black marker (a process called "redacting") before handing the book to the public. Doing this by hand is slow, boring, and prone to mistakes. If the librarian misses a secret, it's a big problem; if they cover up too much, they hide things that should be public.
This paper is about building a smart robot assistant to help the librarian do this job faster and better, specifically for a tricky type of secret called "deliberative process privilege." This is the rule that protects the government's internal brainstorming (the messy drafts, the "what if" ideas, and the private opinions) so that officials can speak freely without fear of public backlash before a decision is made.
Here is how the authors tried to build this robot:
1. The Problem with "Cloud" Robots
Most people think of using a super-smart, cloud-based AI (like a giant brain in a data center) to do this. But the authors say, "Wait a minute!" If the government is reading secret documents, they can't just send those pages to a third-party cloud company. It's like mailing your top-secret diary to a stranger to ask for advice. It's legally and politically risky.
So, the authors decided to build a local robot. They used a smaller, open-source AI model (called Qwen3.5 9B) that can run on a regular computer, right inside the government's own secure building. It's like having a private tutor in the room rather than calling a stranger on the phone.
2. Teaching the Robot: The "How-To" Guide
The authors didn't just ask the robot, "Is this sentence a secret?" They tried eight different ways to talk to the robot to see which method worked best. Think of these as different teaching styles:
- Zero-Shot: Just asking the question directly. "Is this a secret?" (The robot has to guess based on what it already knows).
- Few-Shot: Showing the robot five examples of secrets and five examples of non-secrets before asking the question. "Here are some examples; now you try."
- Error-Based Few-Shot: Showing the robot examples of tricky cases where it previously made a mistake, so it can learn from its errors.
- Chain-of-Thought (CoT): Asking the robot to "think out loud" before answering. Instead of just saying "Yes," the robot must first ask itself: "Was a final decision made yet? Is this just an opinion?" and then answer.
- Multi-Agent: Setting up a team of three robots. One guesses, a second one critiques the guess, and a third one acts as a judge if they disagree.
3. The Results: Who Won the Race?
The authors tested these methods against older, traditional computer programs and a famous commercial AI (Gemini 2.5 Flash).
- The "Think Aloud" Strategy Won: The best method for their local robot was a combination of Chain-of-Thought (making the robot explain its reasoning) and Error-Based Few-Shot (showing it the tricky mistakes it made before).
- The Goal: In this specific job, it is better to be "over-cautious." If the robot misses a secret (a "false negative"), sensitive info leaks. If it covers up too much (a "false positive"), it's just annoying but safe. The authors wanted the robot to catch everything (high "recall").
- The Surprise: The local robot, using this special "think aloud" method, performed almost as well as the giant commercial cloud AI. This is huge news because it means governments can use powerful AI without sending their secrets to the cloud.
4. What Makes a Sentence a "Secret"?
The authors also looked at why the robot decided certain sentences were secrets. They found that "deliberative" sentences (the ones that need redacting) have a specific "fingerprint":
- They sound like opinions: They use words like "I think," "we suggest," "we could," or "it would be good."
- They use "First-Person" pronouns: Lots of "I," "we," and "us."
- They look to the future: They talk about what might happen, not what has happened.
If a sentence is just a fact ("The meeting happened at 2 PM"), the robot knows to leave it alone. If it's a private opinion ("I think we should fire him"), the robot knows to cover it up.
The Bottom Line
The paper concludes that you don't need a massive, expensive, cloud-based supercomputer to help the government redact sensitive documents. A smaller, local AI, if taught to "think step-by-step" and learn from its past mistakes, can do the job almost as well as the big guys. This allows governments to keep their data secure on their own computers while still using modern AI to speed up the process of sharing information with the public.
Drowning in papers in your field?
Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.