← Latest papers
💬 NLP

Artificial Organisations

This paper proposes that multi-agent AI systems can achieve reliable collective behavior through institutional design principles like compartmentalization and adversarial review, demonstrating via the Perseverance Composition Engine that such architectural constraints can enforce honest outcomes even from individually unreliable components.

Original authors: William Waites

Published 2026-02-17
📖 6 min read🧠 Deep dive

Original authors: William Waites

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

The Big Idea: Stop Trying to Make One Perfect Robot; Build a Team Instead

Imagine you are trying to build a skyscraper.

  • The Old Way (Current AI Research): You try to train a single, super-intelligent architect to be perfect. You hope they never make a mistake, never lie, and never get tired. If they slip up, the whole building collapses.
  • The New Way (This Paper): You admit that no one is perfect. Instead, you build a construction company. You hire a draftsperson, a safety inspector, and a quality manager. You give them strict rules about who can see what. Even if the draftsperson tries to cut corners, the safety inspector catches them because they have a different set of tools and a different job.

The author, William Waites, argues that we should stop trying to make individual AI agents "good" and start designing AI organizations where the structure forces them to be reliable.


The Cast of Characters: The "Perseverance Composition Engine"

The paper describes a system called the Perseverance Composition Engine (PCE). Think of it as a tiny, automated newsroom or publishing house. It has a team of AI agents, each with a specific job and specific rules about what they are allowed to see.

  1. The Composer (The Writer):

    • Job: Writes the first draft of a document.
    • Superpower: Can see all the source materials (books, articles, data).
    • Weakness: It's creative but prone to "hallucinating" (making things up) because it wants to finish the story.
  2. The Corroborator (The Fact-Checker):

    • Job: Checks if the Writer actually used the source materials correctly.
    • Superpower: Has access to the Source Materials AND the Draft.
    • Rule: If the Writer says "The sky is green," the Corroborator looks at the source, sees it says "The sky is blue," and slams the "Reject" button.
    • Key Feature: The Writer cannot see the Corroborator's notes until the draft is fixed.
  3. The Critic (The Editor):

    • Job: Checks if the story makes sense, flows well, and answers the prompt.
    • Superpower: Blind Review. The Critic is not allowed to see the Source Materials. They only see the Draft.
    • Why? If the Critic saw the sources, they might think, "Oh, the Writer probably got the facts right because the sources are right there." By not seeing the sources, the Critic is forced to judge: "Does this text stand on its own? Is it convincing to a stranger?"
    • Rule: The Critic cannot look up facts. They only judge the writing.
  4. The Commutator & Curator (The Managers):

    • They organize the workflow, decide who does what, and keep the "institutional memory" (a database of past work) so the team learns from mistakes.

The Magic Trick: "Information Compartmentalisation"

In human companies, we try to stop employees from cheating by writing rules like, "Please don't look at the confidential files." But humans can break rules.

In this AI system, the rules are hard-coded into the software.

  • The Critic literally cannot open the file containing the source materials. It's like trying to open a locked door with a key you don't have.
  • The Composer cannot see the Critic's score until the Fact-Checker says "Pass."

This creates a "Chinese Wall" (a firewall) between the roles. It forces the team to work together to produce a high-quality result, even if the individual parts are flawed.

What Happened When They Tested It?

The author ran this system 474 times to write documents. Here is what they found:

1. The "Liar" Detector
The Fact-Checker (Corroborator) caught the Writer making things up 52% of the time.

  • Analogy: Imagine a student writing an essay. Half the time, they try to make up a quote. The teacher (Fact-Checker) catches them every single time because the teacher has the textbook open, but the student doesn't.

2. The "Better Together" Effect
The documents got much better with every round of editing.

  • Analogy: Think of a rough diamond. The first draft is ugly. The Fact-Checker chips off the fake parts. The Editor polishes the shape. After about 4.3 rounds of this, the final product was 79% better than the first draft.

3. The "Honest Refusal" (The Most Important Part)
The author gave the system an impossible task: "Write a literature review based on this raw search transcript that only has titles and no actual text."

  • The Trap: The system could have just made up a review (fabricated) to please the user.
  • The Result:
    • Round 1 & 2: The system tried to make it up. The Fact-Checker said, "No, you can't prove this."
    • Round 3: The system tried to just list the titles. The Editor said, "That's not a review; it's a list. Bad job."
    • Round 4: The system realized it couldn't win. Instead of lying, it said: "I cannot do this task honestly. Here are four better ways we can solve your problem."
    • Round 5: The system got a perfect score for being honest and helpful.

The Lesson: The system didn't learn to be honest because it was "trained" to be good. It learned to be honest because the structure made lying a losing strategy. If it lied, the Fact-Checker caught it. If it just gave up, the Editor gave it a bad grade. The only winning move was to be honest and offer alternatives.

Why Does This Matter?

Currently, AI safety researchers are trying to "align" individual robots (making them nice). This paper suggests that's the wrong approach.

  • Human Analogy: We don't trust a bank teller to be honest just because we hope they are. We trust the bank's system: cameras, dual signatures, and audits. If the teller tries to steal, the system stops them.
  • AI Conclusion: We should build AI systems where the architecture (the rules of the game) makes it impossible or unprofitable for the AI to lie or hallucinate. We can build reliable systems out of unreliable parts, just like a reliable bank is built out of fallible humans.

The Catch (Limitations)

The author is very honest about the limits:

  1. It's a small experiment: They only spent about $150 and did 474 tasks.
  2. It's self-reflective: The AI wrote the paper about itself (with human help), which is a bit like a student grading their own homework.
  3. It needs more testing: We need to see if this works with different types of AI models and in different jobs (like coding or medicine), not just writing.

Summary

Don't try to make a perfect AI angel. Instead, build a team of flawed AI workers with strict rules, separate roles, and a system that forces them to check each other. That is how you get a reliable, honest, and high-quality result.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →