← Latest papers
🤖 AI

Reliable AI Needs to Externalize Implicit Knowledge: A Human-AI Collaboration Perspective

This position paper argues that achieving reliable AI requires the development of "Knowledge Objects" to externalize and structure implicit knowledge, thereby enabling human verification of critical reasoning patterns that are currently uncheckable and creating a scalable path for improving AI trustworthiness over time.

Original authors: Hengyu Liu, Tianyi Li, Zhihong Cui, Yushuai Li, Zhangkai Wu, Torben Bach Pedersen, Kristian Torp, Christian S. Jensen

Published 2026-05-06
📖 5 min read🧠 Deep dive

Original authors: Hengyu Liu, Tianyi Li, Zhihong Cui, Yushuai Li, Zhangkai Wu, Torben Bach Pedersen, Kristian Torp, Christian S. Jensen

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 Core Problem: The "Black Box" Chef

Imagine you hire a brilliant chef (the AI) to cook a complex meal. This chef has tasted millions of dishes from every restaurant in the world. They know exactly how to combine flavors, when to add salt, and how to fix a burnt sauce.

However, there is a catch. The chef learned these skills by watching millions of people cook, not by reading a formal cookbook.

  • Explicit Knowledge (The Cookbook): This is the stuff the chef can point to. "The recipe says add 2 cups of flour." The chef can show you the page in the book. This is easy to check.
  • Implicit Knowledge (The Chef's Intuition): This is the stuff the chef feels. "Add a pinch of salt because the sauce feels too acidic," or "Don't use this knife because the handle feels slippery." The chef never wrote this down. It's just a pattern they picked up from watching others.

The Paper's Big Claim:
Right now, AI is amazing at using this "Intuition" (Implicit Knowledge) to do smart things. But because it's never written down, we can't check if it's right. The chef might be using a brilliant technique, or they might be copying a bad habit from a terrible restaurant. We can't tell the difference because the "recipe" for that intuition doesn't exist.

This creates a dangerous gap: The AI is very capable, but we can't trust it because we can't see how it decided what to do.


Why Current Fixes Don't Work

The paper looks at four ways people try to fix AI reliability, and explains why they fail to solve this specific problem:

  1. Looking Up Facts (RAG): Imagine the chef is allowed to open a cookbook while cooking. This helps with facts (like "how many eggs in an omelet"), but it doesn't help with the intuition (like "how to judge if the pan is hot enough"). The chef still relies on their invisible gut feeling.
  2. Asking the Chef to Check Themselves: Imagine asking the chef, "Are you sure this tastes right?" The chef might say, "Yes, I'm 99% sure!" But if the chef learned a bad habit from the start, they will confidently say the bad habit is good. They can't spot their own blind spots.
  3. Training the Chef: Imagine giving the chef a new set of rules to follow. This changes their behavior, but the rules are locked inside their brain (the model's parameters). You can't look inside to see which rule made them do something.
  4. Giving the Chef a Notebook (Memory): Imagine the chef writes down what they did today to remember for tomorrow. But if they wrote down a mistake, they will just repeat that mistake forever. The notebook doesn't tell you if the note is "True" or "False."

The Common Flaw: All these methods keep the "Intuition" trapped inside the AI. Humans can't see it, check it, or sign off on it.


The Solution: "Knowledge Objects" (KOs)

The authors propose a new tool called a Knowledge Object (KO).

Think of a KO as a transparent "Recipe Card" for the chef's intuition.

When the AI uses its intuition to solve a problem, it must stop and write down a structured card that says:

  • The Claim: "I used the Singleton pattern for the database."
  • The Reasoning: "I saw 12 other experts do this in high-traffic situations."
  • The Limits: "This only works for Java apps, not for batch processing."
  • The Validator: "Alice (a Senior Engineer) checked this on Jan 15th and said 'Approved'."

How This Changes Everything:
Instead of the AI just giving you an answer, it gives you the answer plus the "Recipe Card" showing how it got there.

  1. It Makes the Invisible Visible: You can now see the reasoning, not just the result.
  2. It Allows Human Check-ups: A human expert (like Alice) can look at the card and say, "Yes, that's a good pattern," or "No, that's a dangerous pattern."
  3. It Saves Time (The "Cumulative" Effect):
    • Without KOs: Every time a new developer asks the AI a question, they have to spend 30 minutes checking if the AI is right.
    • With KOs: Alice checks it once. She stamps the card "Verified." Now, the next 1,000 developers see the card, see Alice's stamp, and trust the answer immediately. The work is done once, but the benefit lasts forever.

The "CodeAssist" Example

The paper uses a software example to explain this:

  • The Scenario: An AI helps a programmer decide how to connect a database.
  • The Old Way: The AI says, "Use the Singleton pattern." The programmer has to guess if this is safe or if it will crash the system.
  • The KO Way: The AI says, "Use the Singleton pattern," and shows a card: "Warning: This causes crashes if over 100 people use it at once. Verified by Senior Engineer Alice for standard web apps. Not verified for batch jobs."
  • The Result: The programmer knows exactly when to use it and when to avoid it. They don't have to guess.

Summary

The paper argues that we cannot rely on AI alone because its "brain" contains too much hidden, unverified intuition. To make AI reliable, we need to force it to write down its reasoning in a format humans can check.

By turning hidden intuition into Knowledge Objects, we turn a one-time guess into a permanent, trusted asset. It transforms AI from a "black box" that we have to fear into a collaborative partner where human judgment is recorded, shared, and built upon over time.

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 →