A discipline for governed knowledge

Know what you know. And prove it.

In the age of AI, the signals we used to trust — where a claim came from, who stands behind it, whether it still holds — are disappearing. Knowledge Foundry is a discipline for governing knowledge so that what people, institutions and machines reason from stays traceable, accountable and sound.

The problem

More information. Less trust.

Generative AI produces fluent, plausible content instantly — and strips away the provenance and authorship that once told us what to believe.

The idea

Information is not knowledge.

Knowledge worth relying on has been examined, justified and accepted by someone accountable — and it changes under control.

Knowledge Foundry treats it as a governed object with a life: an origin, evidence, a reasoned justification, an authority who accepts it, and a recorded history of change. Rigour matches the stakes — a working note is held lightly; a board decision is held to account. And it is honest by design: counter-evidence stays attached, and a claim's standing is stated plainly.

01What is this?
02Where did it come from?
03Why should we believe it?
04Who authorised relying on it?
05What has replaced it?

One discipline · three expressions

The same discipline, at every scale.

Knowledge Foundry isn't a platform in search of customers; it's an institutional capability for governed knowledge. Which is why the same discipline serves a single learner, a whole profession, and a university — turning static information into durable, governed capability, and changing only in scale.

For Learning

The discipline works at the scale of one: turn what you read into knowledge you can trust — and keep it. Free to read, nothing to buy.

A discipline for your own knowledge →

For Professional Practice

A credible, non-vendor account of how a profession creates, validates and relies on knowledge — now that AI is in every workflow. Ready to shape into guidance, CPD and conference material a whole body can adopt.

A standard for how your profession knows →

For Higher Education

A rigorous, teachable account of how a claim earns the right to be relied upon — directly relevant to academic integrity and research provenance in the age of AI. Ready as a module, a framework, or a research collaboration.

How knowledge becomes trustworthy →

The architecture barely changes. Only the scale does.

A worked example

Should we move to a four-day week?

Watch a good decision get made — from first question to final call, and back again when the evidence changes.

The stance

We do not make more information. We make knowledge you can trust.

A discipline and open reference architecture — free to read, study and implement. It may be instantiated through many kinds of governed knowledge systems, varying by domain, institution and technology.

Intellectual foundations

An original synthesis of established traditions.

Knowledge Foundry synthesises established work from knowledge engineering, knowledge management, epistemology, records and archival governance, information systems and contemporary AI. The reference architecture is an original synthesis; the underlying problems and principles have deeper disciplinary histories — set out in full, in the open.

This lets you see plainly what is established in prior literature, what Knowledge Foundry derives from it, and what remains an original — and still unvalidated — proposition.

Read

The work, in full and in brief.

Everything is open. Read the short version to understand the idea, or the complete reference architecture to see it entire.

The Reference Architecture — complete manuscriptRead & download →
The Overview — the whole programme on a pageDownload →
The Worked Example — one governed decisionRead
Essays · “What do you actually know?”Read essay 1 →

Start here

New here? Begin with the questions.

Knowledge Foundry is a discipline for governing knowledge — for keeping what people, institutions and machines rely on traceable, justified, accountable, and able to change under control. It is free to read, and it is not a product. This is the short way in.

The test at the heart of it

For anything you rely on, you should be able to answer — and prove — five questions:

01What is this?
02Where did it come from?
03Why should we believe it?
04Who stands behind it?
05Is it still true?

Answer all five, and it is knowledge. Miss one, and it is just something you happen to hold.

See it work

The fastest way in is to watch one ordinary decision governed end to end — should we move to a four-day week? — in plain English, from first question to final call.

Read the worked example →

One discipline, three expressions

The same discipline serves a single learner, a whole profession, and a university — changing only in scale. Find your door:

For Learning — govern your own knowledge, at the scale of oneFor Professional Practice — a standard for how a profession knowsFor Higher Education — how a claim earns the right to be relied upon
LearningProfessional PracticeHigher Education
The unitLearning domainBody of knowledgeCourse
The stewardThe learnerA technical committeeFaculty
The pathLearning pathProfessional standardCurriculum
The checkSelf-evaluationCertificationAssessment
The outputPersonal projectsPractice guidanceResearch
What persistsPersonal memoryOrganisational memoryInstitutional memory
The resultDeveloped capabilityCertified membersGraduates

Choose your depth

The open reference architecture lays out four routes by purpose — understand the idea, understand the discipline, evaluate or implement it, or study the intellectual foundations.

Open the reference →

Go deeper

The idea →FAQ →Open architecture →

The problem

AI can write anything. That is exactly the problem.

For thirty years we made our documents, processes and data legible to machines. That work is nearly done. The layer that actually carries our knowledge — judgement, evidence, the difference between a correct answer and a defensible one — was never built to be governed.

What changed

Generative AI made that layer computable overnight. It can now structure and reason over an organisation's knowledge at a scale never possible before. But a system is only as sound as the knowledge beneath it, and ungoverned knowledge does not scale — it multiplies error, confidently.

The real gap

The gap is not the machine's ability to answer. It is our inability to say where an answer came from, why it should be believed, and who is accountable for it. That is a gap in governance, not technology — and it is the one Knowledge Foundry closes.

The question is no longer whether a system can produce an answer. It is whether you can stand behind the one it gives.

Next — the idea

The idea

Treat knowledge as a governed object, not a file.

The distinction the whole discipline turns on is simple: information is content; knowledge is content that has been examined, justified and accepted by someone accountable, and that changes under control.

Information is not knowledge: governance adds source, reasoning, ownership and a shelf life.

A life, not a document

A governed knowledge object carries its origin, the evidence and reasoning behind it, the authority who accepted it, and its history as it is revised or retired. It can be inspected, questioned and trusted — because every step is on the record.

Proportionate, not bureaucratic

Rigour matches the stakes. A working note is held lightly; a board decision is held to account. The same discipline covers both; only the depth changes.

Honest by design

Governed knowledge makes uncertainty visible rather than hiding it. Counter-evidence stays attached; a claim's standing is stated plainly. Trust is earned by being sound, not by being loud.

The five questions: what is this, where did it come from, why believe it, who stands behind it, is it still true?

This is not a tool you buy. It is a discipline you adopt — set out in full as a reference architecture, and free to read.

The architectureRead & download

The reference architecture

The whole discipline, set out to be inspected.

Knowledge Foundry is published as a complete reference architecture — from the principles that never change to the tests that prove an implementation honours them. It is technology-neutral: it says what must be true, not which software must be used.

From principle to practice: four levels, each serving the one above.

Four levels

A lower level chooses how to satisfy a higher one; it may never quietly revise it.

01Principlewhat is always true
02Methodhow we act on it
03Architecturewith what structures
04Implementationin a specific deployment

What it covers

The lifecycle of a knowledge object from capture to retirement; how much rigour a decision deserves; who may make a decision consequential; and how any of it can be reconstructed and shown to conform.

The full architecture is available to read and download.

Read & download

A worked example

Should we move to a four-day week? Watch a good decision get made.

To show the discipline without jargon, we follow one ordinary decision from first question to final call — and back again when the evidence changes.

01

The question is posed and the evidence gathered — real trials, real counter-evidence. Each source is weighed.

02

A reasoned case is written, with its assumptions stated and its limits admitted: warranted for a trial, not yet for permanent adoption.

03

An authority — the executive team — accepts it for a defined use.

04

It informs the decision, is monitored, is revised when the trial reports, and is eventually folded into a broader policy.

05

Nothing is erased; the whole history can be reconstructed.

Nothing here depended on working hours. Swap the subject — a clinical guideline, a research finding, a strategy — and every step is the same. That is the point.

Knowledge Foundry for Professional Practice

A standard for how your profession knows.

Your members create, validate and rely on knowledge every day — and AI is now in every one of those workflows. Knowledge Foundry gives you a credible, non-vendor account of how professional knowledge should be governed, ready to shape into guidance your members can adopt.

What it looks like

Suppose a professional body issues new sustainability-reporting guidance. Today that usually means a PDF, a newsletter, a webinar and an FAQ — four disconnected artefacts, and a member left to work out what changed and which version now governs. Held as a governed knowledge object, the same guidance carries links to the standards it interprets, the earlier guidance it supersedes, the worked examples that show it in practice, and a record of who approved it and when. The aim is that a member stops searching and starts navigating — and that when a committee rotates, the reasoning behind the guidance doesn't leave with it.

Adoptable

Adoptable guidance

A framework your members can put to work, not a product to buy.

Ready

CPD and events

Material for webinars, conference sessions and continuing development.

Independent

Credibility

A rigorous, independent foundation your association can put its name to.

Use and extend the architecture

Examine how your guidance, standards and accepted practice are created, revised and relied upon
Co-develop a practice framework or guidance note from the architecture
Convene a working group to adapt it to your field
Contribute evidence and proposals from real use
Start a conversation

Knowledge Foundry for Higher Education

How knowledge becomes trustworthy — teachable, and rigorous.

Academic integrity and research provenance are under new pressure in the age of AI. Knowledge Foundry offers a disciplined, teachable account of how a claim earns the right to be relied upon — directly relevant to how your institution teaches, researches and governs its own knowledge.

What it looks like

Consider a Corporate Finance course. Instead of a fresh pile of slides, notes and readings each semester — recreated, rarely connected — the subject becomes a governed knowledge domain: the canonical concepts, the explanations and worked examples, the evidence behind each claim, the assessment tied to stated outcomes, and the research that keeps it current. The aim is that every cohort improves the same asset rather than rebuilding it — so knowledge accumulates instead of resetting, teaching and research feed each other, and what the department knows survives the turnover of who happens to teach it.

Teachable

Teaching material

A ready module on how knowledge becomes trustworthy, for any discipline.

Governance

Integrity and provenance

A framework for research governance and academic integrity in the AI age.

Open

A research programme to align with

An open, citable body of work.

Use and extend the architecture

Teach how knowledge earns the right to be relied upon
Build a curriculum module on the discipline
Run a departmental or research pilot
Contribute findings and limitations back to the architecture
Start a conversation

Knowledge Foundry for Learning

A discipline for your own knowledge.

You consume more than ever — books, papers, threads, and now answers from AI about anything. But can you say what you actually know: where it came from, why you believe it, and whether it still holds? The discipline works at the scale of one. Apply it to your own learning and your notes stop being a pile of information and become knowledge you can reason from — and trust.

What it looks like

Take someone learning AI engineering. Instead of scattering the work across a dozen tools — notes here, highlights there, half-remembered answers from a chatbot — they build one governed domain: the sources they trust, the concepts they've worked out, the experiments they've run and what each showed, the projects that turned understanding into capability. The aim isn't a bigger pile of notes; it's knowledge that compounds — where a claim relied on a year ago still carries its source and its reasoning, and what's been learned becomes something to build on, teach, and stand behind.

Clarity

Know what you know

Separate the information you've collected from the knowledge you can rely on — and make your confidence, and your uncertainty, explicit.

Provenance

Keep the why

Hold on to where a claim came from and why you believed it, so a note written a year ago still means something — to you, or to a machine you hand it to.

Under control

Learn without overwriting

Update what you know as you learn more, without silently erasing your past reasoning. Light for a passing note; rigorous for a belief you will act on.

Where to start

The worked example — one decision, governed end to end. The same moves apply to your own learning.
The overview — the whole discipline on a page.
The essays — short pieces that teach it one idea at a time. Coming soon.
Read the work Start with the idea

Read

The work, in full and in brief.

Everything is open. Read the short version to understand the idea, or the complete reference architecture to see it entire.

The Reference Architecture

The complete programme manuscript.

Read online →
The Overview

The whole programme on a page.

Download →
The Worked Example

One governed decision, end to end.

Read
What do you actually know?

Essay 1 · the core idea

Read →
Being right isn't enough

Essay 2 · being right vs being trusted

Read →
Knowledge has a shelf life

Essay 3 · why knowledge must change

Read →

Citable, versioned, and free to read.

← Read & download

Essay 01

What do you actually know?

You've read a thousand things. Almost none of them are knowledge yet — and in the age of AI, that difference is the whole game.

Think of something you're sure you know. Not a fact you'd look up — something you'd act on. That a certain way of eating works. That your field is moving in a particular direction. That an investment is sound, or a study you read last year proved a thing.

Now try to reconstruct it. Where did it come from? What was the actual evidence, as opposed to the headline? What would have to be true for it to be wrong — and do you know whether it is? When did you last check?

For most of what we carry around, the honest answer is: I can't say. We have a library in our heads we can't cite.

This isn't a memory problem, and it isn't a matter of trying harder. It's a category problem. We treat information — the things we've read, watched, highlighted, half-remembered — as though it were knowledge. It isn't, not yet. And the difference has never mattered more, because we now have machines that produce fluent, confident, sourceless information about anything, on demand. The pile keeps growing, and the ground under it keeps getting softer.

Information is not knowledge

Information is content you've encountered. Knowledge is content you've examined — that you can stand behind, that carries its reasons with it, and that you can change without losing the thread. The gap between the two is work, and it's the work almost no one does on their own reading.

Here's the test. For anything you rely on, can you actually answer — not gesture at:

- What is this, exactly? The claim, not the vibe of it. - Where did it come from? The source, and how good the source was. - Why do I believe it? The reason — including the best case against it. - How sure am I? Certain, leaning, or just repeating something? - Is it still true? What's changed since I decided this?

If you can answer those, the thing is knowledge. If you can't, it's a rumour you happen to hold. Most of what any of us "knows" is the second kind — and we find out the hard way, when we repeat it and get challenged, or act on it and it fails.

Governing your own knowledge

The good news is that turning information into knowledge doesn't take more reading. It takes a few small habits — the same discipline serious institutions use to govern what they know, applied at the scale of one.

Keep the source with the claim. A claim without its origin isn't knowledge; it's a floating sentence. When you note something worth keeping, capture where it came from and how strong that source was in the same breath. Your future self can't reconstruct a provenance you never wrote down.

Write the reason, not just the conclusion. The thing worth keeping isn't "four-day weeks improve productivity." It's why you believe that, and what would change your mind — the best evidence and the best counter-evidence, side by side. A belief with its reasoning attached can be defended, questioned, and updated. A bare conclusion can only be asserted.

Mark how sure you are. There's a world of difference between "I know this," "I think this," and "I'm relying on this without having checked." Say which. Making your own uncertainty visible isn't weakness — it's the thing that tells you where to look next. Most bad decisions are things we were sure of for no recorded reason.

Update without overwriting. When you learn something that changes a belief, don't quietly swap the old version and pretend you always thought so. Note what changed and why. The trail matters — partly because you'll want it later, and partly because a belief that has survived a recorded revision is worth far more than one that has never been tested.

And don't do this for everything. This is the part people miss. A passing curiosity needs none of it. A claim you're going to act on, teach, or repeat in public earns all of it. Spend the effort where the stakes are; the discipline isn't rigour for its own sake, it's rigour matched to what you're going to rely on.

None of this is a system to buy or an app to install. It's a way of holding what you learn. You can do it in a notebook.

Why now

You could have ignored all of this ten years ago and mostly gotten away with it. Reading was slow, sources were visible, and the friction of finding things did some of the filtering for you.

That friction is gone. A model will now produce a confident, well-written, entirely sourceless answer to any question you ask, in seconds — whether or not it's true, whether or not anyone stands behind it, whether or not it was true yesterday. The fluency is total; the provenance is zero. That is a genuinely new situation, and it's precisely the one these habits were built for.

If you can't govern your own knowledge, you won't be able to tell your understanding apart from a plausible paragraph a machine generated for you. From the inside, they feel the same. The only defence is to know — for the things that matter — what you actually know: where it came from, why you believe it, and whether it still holds.

The point

The goal was never to know more. Knowing more is easy; it's just consumption, and we're drowning in it. The goal is to know what you know — to be able to stand behind it, to yourself first. That isn't a productivity trick. It's a quieter, older thing: the difference between having read about something and actually understanding it, made deliberate.

You've read a thousand things. Pick the handful you're going to rely on, and make them knowledge.

This is one idea from Knowledge Foundry, a discipline for governing knowledge in the age of AI. The same five questions scale from a single learner to an entire institution — the subject changes; the discipline doesn't.

Next · Being right isn't enough →
← Read & download

Essay 02

Being right isn't enough

A good argument and a claim someone will stand behind are two different things — and in the age of AI, the gap between them is where the risk now lives.

You have probably written the memo. The analysis was sound: the evidence was there, the reasoning held, you'd even handled the obvious objections. You sent it. And then nothing moved. Six months later the organisation did roughly the opposite, and if you asked why, no one could quite say. You were right, and it changed nothing.

Now the other version, which is worse. Everyone was relying on a number — in the forecast, the model, the board pack. It had been there for years. Then it turned out to be wrong, and as the damage was counted, a strange thing surfaced: there was no one to hold responsible. Not because people were hiding, but because no one had ever actually decided to rely on it. It had simply accumulated. Everybody trusted it because everybody else did.

These two failures look like opposites — one where a good claim goes nowhere, one where a bad claim goes everywhere. They have the same root. Both confuse two things a serious organisation has to keep apart: whether a claim is justified, and whether anyone has accepted it.

Two different acts

Justification is the case for a claim: the evidence, the reasoning, the counter-argument met. It lives entirely inside the claim. A thing is justified or it isn't, regardless of who is looking at it.

Acceptance is a different act altogether. It is a person — or a body — with the authority to do so deciding that we will rely on this, and taking responsibility for that reliance, within a stated scope. Acceptance isn't about whether the claim is good. It's about whether anyone is willing to stand behind acting on it.

You can have either without the other, and once you notice the distinction, you see both gaps everywhere.

Justified, but never accepted

The correct memo that changes nothing is a claim that was justified but never accepted. This is the quiet grief of every capable person in a large organisation: the belief that being right ought to be enough. It isn't, and it was never going to be. Being right earns a claim the right to be relied upon. It does not cause the reliance. Somebody accountable has to take the second step — to say, in effect, "yes, we are going to act on this, and I will own that we did." Without that step, the best analysis in the building is a very good document and nothing more.

If you have ever been that person, the lesson is not "argue harder." It is that your correct thing needs an owner, not just an audience.

Relied upon, but never accepted

The number everyone trusted and no one owned is the mirror image: reliance without acceptance. This one is more dangerous, because it fails silently and leaves no one accountable. Reliance tends to accrete by default — a figure gets used once, then cited, then built on, until an entire structure rests on something nobody ever signed off. There was no moment when a named person said "I accept that we depend on this." So when it breaks, there is no owner, because ownership was never taken.

Organisations walk into their worst failures this way — not through a bad decision, but through the absence of a decision everyone assumed someone else had made.

Acceptance is a real act, not a rubber stamp

This is why acceptance, done properly, is specific and accountable: someone with the authority, taking responsibility, for a defined scope of reliance — we will rely on this for this, and not for that — at a moment you could point to afterwards. It is the point where a claim stops being an argument and becomes something the institution stands behind.

A profession's standard of practice, a board's sign-off, a regulator's approval, an editor's decision to publish — at their best these are all the same move: turning a justified claim into an accepted one, and putting a name to the reliance. Strip the name away and you don't have a faster process; you have an accountability vacuum with good production values.

Why this matters more now

Justification has become cheap. A model will generate a fluent, well-structured, superficially rigorous case for almost any claim you like in seconds — and an equally fluent case against it. Arguments are no longer scarce. The appearance of justification is now essentially free.

Which means the load-bearing act is no longer producing a good argument. It is acceptance — a named, accountable person or body deciding to rely on something, within a scope, and owning that reliance. When the machine can justify anything, "is there a good case for this?" stops being a useful filter, because there is always a good case for everything. The only question left with any weight is the old one: who is accountable for us relying on this?

We are entering a period where justification is abundant and acceptance is scarce. Scarce things are where both the value and the risk concentrate.

From one mind to many

At the scale of one, you already do a version of this. The difference between "I have convinced myself this is right" and "I am going to act on this" is exactly the difference between justifying a claim and accepting it — and knowing which you are doing is half of thinking clearly.

At the scale of a team, a profession, or an institution, the same distinction has to be made deliberate and visible, because the reliance is shared and the consequences land on people who were never in the room. That is what standards bodies, review boards, and sign-off processes are for. It is also, not coincidentally, exactly what erodes first when everyone is moving fast and the machine is producing confident answers on demand.

The point

Being right is necessary. It has never been sufficient. The claims a profession actually runs on — the ones that hold up when they are challenged, and have someone to answer for them when they don't — are the ones somebody was willing to stand behind. In an age when anything can be argued, the argument is the cheap part. The signature is the scarce one.

This is one idea from Knowledge Foundry, a discipline for governing knowledge in the age of AI. It draws a hard line between justifying a claim and accepting it for reliance — because the institutions we trust are built on the second, not the first.

Next · Knowledge has a shelf life →
← Read & download

Essay 03

Knowledge has a shelf life

Everything you know was true as of some date you probably can't name. Keeping knowledge trustworthy was never about getting it right once — it's about how you let it change.

Somewhere in your organisation there is a number that was correct in 2019 and has been quietly wrong ever since. A policy written for a world that no longer exists. A rule of thumb everyone still repeats, from a study that has since been overturned. No one is being careless. The claim was right when it was made; it simply expired, and no one was watching the date.

Now look inward. The advice you give, the assumptions you run on, the things you're confident about in your own field — when did you last actually check any of them? Most of what any of us knows was true as of some moment we can't name, and we have no idea which of our beliefs have quietly gone off.

This is the uncomfortable fact underneath everything: knowledge decays. Not because anyone changed the claim, but because the world moved and the claim didn't. A statement that was well-evidenced and true can rot into a confident falsehood without a single word of it changing — because what changed was outside it. Being right, it turns out, is not a possession you get to keep. It's a reading taken at a particular time.

The obvious fix, and the trap inside it

The obvious response is: update more. Keep everything current. That instinct is right — and it walks straight into a second, subtler failure that quietly does more damage than staleness ever could.

Call it the silent overwrite. Knowledge gets updated, but with no record that it changed. The document now says X. Last year it said Y. Nobody can tell, nobody can say when it flipped, and nobody can reconstruct why. You have kept your knowledge current and, in the same motion, destroyed your memory of it.

This sounds minor. It is not. An organisation that overwrites its knowledge in place loses three things it cannot function without.

It cannot audit its own past decisions, because it can no longer see what it knew at the time. Was that call wrong when it was made, or simply overtaken by events? Those are completely different verdicts, and you cannot tell them apart once the earlier version is gone.

It cannot learn, because learning means seeing your own trajectory — and it has erased the trajectory, keeping only the latest frame.

And it cannot answer the simplest challenge — why do we do it this way? — with anything better than "no one remembers." The reasoning was overwritten along with the conclusion.

Change under control

So the failure is not change. Change is not the enemy; ungoverned change is. Knowledge that stays trustworthy neither stands still nor gets rewritten in the dark. It evolves under control — which turns out to mean a few specific things.

You update deliberately, not by accident. You record what changed, and why. You preserve the old version rather than deleting it — it is superseded, not erased, so the trail survives. And a changed claim has to re-earn the trust the old one held; last year's version being accepted does not mean this year's inherits that standing automatically. (That's the thread from the previous essay: a new version has to be accepted again, by someone accountable — justification doesn't carry over just because the file name did.)

There is one more piece, quiet but decisive: currency. A claim worth relying on should carry not only is this true but when was this last checked, and what would trigger a review. A belief with an expiry condition attached is one that can tell you when to stop trusting it. Almost nothing we carry has one — which is exactly why so much of it goes off without our noticing.

Why the trail is the whole point

Notice what the trail actually buys you. Kept properly, it lets you tell "we were wrong" apart from "the world changed" — two sentences that pose as excuses for each other and are in fact opposite lessons. One means fix your reasoning; the other means update your inputs. You can only distinguish them if you kept the record of what you believed, when, and on what basis.

An institution that can see how its knowledge changed over time has a memory, and can improve. One that only ever sees the current version has a present, and quietly repeats itself.

Why this matters more now

All of this used to be a slow problem. It isn't anymore. The substrate under our knowledge is now being rewritten continuously and silently, at a scale we have never had to manage. Ask a model the same question twice and you may get two different answers, with no note of what moved between them. The answer that was authoritative in one session is gone in the next — no changelog, no superseded version, no trace. It is ungoverned evolution as a default setting.

Build on that, and you inherit claims with no shelf life and no lineage: no way to tell current from stale, no way to reconstruct why the ground shifted under a decision you made last month. The faster knowledge is regenerated, the more it matters that some of it is held under control — dated, tracked, able to account for its own changes. When the world's information keeps no memory, keeping yours is not bureaucracy. It is the advantage.

The point

Three things hold across these essays. Know what you actually know, and not merely what you've read. Know who is accountable for what you rely on. And know when it changed, and why. None of the three is a filing system. Together they are the difference between a mind — or an institution — that learns, and one that drifts, confidently, into being wrong.

The goal was never knowledge that never changes. That is just knowledge going quietly stale. The goal is knowledge that changes in the open — so that you can always say what you believe now, what you believed before, and what moved you between them.

This is one idea from Knowledge Foundry, a discipline for governing knowledge in the age of AI. It treats change as normal and silence as the danger: knowledge should evolve under control, keeping the trail that lets you tell growth from drift.

Back to Read & download

Open architecture

Use, study, and extend the architecture.

Knowledge Foundry is published as an open reference architecture. Anyone may read, study, cite and implement it — subject to a clear licence and to an honest account of how it is governed. Publishing it this way is itself an instance of the discipline: the work is inspectable, attributable, versioned, and open to evidence-based change.

Status

Open reference architecture · Public Review Release 0.1. The architecture is complete and internally consistent; parts remain open to testing and revision through evidence from real use.

Licence

The documentation and diagrams are published under a Creative Commons Attribution 4.0 licence (CC BY 4.0): you may share and adapt them, including commercially, provided you give appropriate credit and indicate changes. Any schemas, templates or code released later will carry an appropriate open-source licence.

The name “Knowledge Foundry” and its marks are governed separately from the content licence, so that no one may imply endorsement or falsely claim conformance. The licensing position is being finalised and is subject to legal review before it is settled.

Stewardship

The architecture is currently edited and stewarded by its founding editor (see About). Authority over what is accepted into the reference architecture is attributable, and stewardship may broaden to a named review group as the work matures.

Corrections, proposals and evidence

This is a public review release, and critique is welcome. Corrections, proposals, and evidence or limitations found in real implementations can be sent to hello@knowledgefoundry.org. A public repository for transparent issue-tracking and revision is planned.

Conformance

To keep claims honest, three levels are distinguished:

Inspired by — draws on Knowledge Foundry’s ideas, without claiming to implement them.
Implements elements of — puts specific parts of the architecture into practice.
Conforms to — meets the stated requirements of a named Knowledge Foundry version, and can show it.

Only the third is a conformance claim, and it is always made against a specific version.

Cite it

Knowledge Foundry Reference Architecture (Public Review Release 0.1), knowledgefoundry.org. Individual documents may be cited by their KF code and version — for example, KF-1000 Canon, v0.1.

Frequently asked

Enter the work through your own questions.

Knowledge Foundry is a dense body of work. These answers are an orientation layer — short and honest, and linked into the reference where each question is treated in full. The hard ones are here too.

Understanding Knowledge Foundry
What is Knowledge Foundry?

A discipline — and an openly published reference architecture — for governing knowledge so it stays trustworthy as it moves between people, institutions and machines. It sets out the principles, methods and structures through which knowledge can remain traceable, justified, accountable and able to change under control. It is a body of work to study and apply, not a product to buy.

What problem is it trying to solve?

As knowledge passes from whoever created it to everyone who later relies on it — and now through AI systems — it tends to shed the things that made it trustworthy: where it came from, why it was believed, who stood behind it, and whether it still holds. Knowledge Foundry is a disciplined way to keep those attached.

Is it a discipline, a methodology, or a software architecture?

Primarily a discipline: a coherent account of what governed knowledge requires. It contains a method — a lifecycle — and a reference architecture — the structures that carry it — and it can be implemented in software. But the discipline comes first, and no particular software is mandated. See the Canon.

What does “governed knowledge” mean?

Knowledge you can rely on because its provenance, justification, ownership and currency are maintained deliberately, not left to chance. Governance here does not mean bureaucracy; it means the difference between information you happen to hold and knowledge you can stand behind.

What is a knowledge object?

The central unit of the discipline — an Operational Knowledge Object: a piece of knowledge treated as something with a life, carrying its origin, its evidence, an accountable owner, and a controlled way of changing. See the Lifecycle.

Why aren’t documents enough?

A document holds content, but not the governance around it. You cannot tell from a file alone where a claim came from, who authorised relying on it, or whether it has been superseded. Knowledge Foundry governs the knowledge, not just the document that happens to carry it.

Why does this matter more in the age of AI?

Generative AI produces fluent, authoritative-sounding content instantly, while stripping away the signals we used to judge it by. That makes the governed distinction — between information and knowledge you can warrant — scarcer and more valuable, not less.

How it relates to adjacent fields
Isn’t this just knowledge management with new terminology?

No. Knowledge management is largely about capturing, storing and sharing content. Knowledge Foundry is about the conditions under which knowledge earns the right to be relied upon: justification, acceptance, accountable authority, and governed change. It is closer to the governance of a claim than the management of a file — and where it overlaps with KM, it says so. See the Literature Landscape.

How is it different from a “second brain” or personal knowledge management?

PKM helps an individual capture and organise what they have read. Knowledge Foundry addresses what happens when knowledge must be relied upon beyond its original creator — traceable, justified, shareable, accepted, maintained. It works at the scale of one, but it is built for knowledge that outgrows the note-taker.

How does it relate to knowledge engineering?

Knowledge engineering — representing knowledge so machines can use it — is one of its deepest roots. Knowledge Foundry draws on it and adds the governance layer: not just representing knowledge, but keeping it warranted and accountable over time. See The Evolution of Knowledge Engineering.

What does it take from records and archival governance?

The insight that provenance, retention, supersession and accountable custody are not optional extras but the substance of trustworthiness. Archival practice has governed the lineage of records for a very long time; Knowledge Foundry brings that discipline to operational knowledge.

Is human judgement genuinely preserved, or just turned into workflow steps?

Judgement is central, and it stays human. The architecture makes explicit where judgement is exercised — who justifies a claim, who accepts it, who is accountable — rather than replacing it. Naming those moments makes the human decisions harder to skip, not easier. See the Authority framework.

AI and technology
Is Knowledge Foundry an AI system? Does it depend on generative AI?

No. It is a discipline for governing knowledge, whether that knowledge is produced by people or by machines. It is especially useful now because of AI, but it does not require generative AI, and it is not a model or a product.

How is it different from RAG, knowledge graphs, or enterprise search?

Those are retrieval and representation technologies — ways to find or structure information. Knowledge Foundry asks a different question: not “can I find it?” but “should I rely on it, and can I prove why?” It governs provenance, justification, authority and currency, and can sit above any of those technologies.

How does it address AI hallucination?

Not by fixing the model, but by governing what a system is allowed to treat as knowledge. A governed knowledge object carries its source and justification, and an accountable authority accepts it — so fluent, unsourced output cannot quietly become “what the organisation knows.”

Which decisions must stay human — could AI eventually perform acceptance and assurance?

Acceptance, and accountable authority, are human by design: someone must be answerable for what is relied upon. AI can assist at every step — drafting, checking, surfacing evidence — but the warrant to rely, and the accountability for it, rest with a person or body. Whether that should ever change is a live question the architecture is built to make visible, not hide.

Does it prescribe a technology stack? Can it work with Obsidian, SharePoint, Confluence or Notion?

It is technology-neutral: it says what must be true, not which software to use. It can be applied on top of tools like those — they hold content; the discipline governs the knowledge. See Open Architecture.

What is a Knowledge Operating System, and is it required?

A Knowledge Operating System is one implementation pattern — a way of building software that enacts the architecture. It is a possible destination, not the required one. The discipline can be applied with far lighter means, and implementations are expected to vary by domain, institution and technology.

Using it
Who is it for? Can an individual use it? Can associations and universities?

All three, at different scales — the same discipline expressed as Learning, Professional Practice and Higher Education. An individual can apply it to their own knowledge; a profession can govern its body of practice; a university can govern teaching, research and its own knowledge. The architecture barely changes; only the scale does.

Must you implement the whole thing? Can it be adopted incrementally?

No, and yes. The architecture is complete so it can be inspected as a whole, but it is meant to be adopted proportionately. A minimum viable implementation governs a single important knowledge object end to end — which is exactly what the worked example shows.

Doesn’t governance create bureaucratic burden?

It can, if applied uniformly — which is why it should not be. Governance is proportionate to materiality: trivial knowledge gets light treatment; consequential knowledge earns more. The point is to spend rigour where reliance is high, not everywhere. See Materiality & Assurance.

How does a claim move from a source to accepted use, and how is outdated knowledge retired?

Through a lifecycle — capture, structuring, evaluation, justification, acceptance, operational use, governed evolution, and retirement — each step explicit about who does what and why. Knowledge that no longer holds is not silently overwritten; it is superseded or retired, with a record of what replaced it. See the Lifecycle.

Openness and governance
What does “open architecture” mean here? Is it free? Can it be adapted?

The whole architecture is free to read, study, cite and implement. The documentation and diagrams are licensed CC BY 4.0 — you may share and adapt them, including commercially, with attribution. The name and marks are governed separately, so no one can falsely claim conformance. See Open Architecture.

Who governs it, and how are changes made?

It is currently edited and stewarded by a named founding editor, with authority over what is accepted kept attributable — as the discipline itself requires. This is a public review release: corrections, proposals and evidence from real use are welcome, and stewardship may broaden to a review group as the work matures. See Open Architecture.

Can organisations claim conformance? Can commercial organisations use it?

Yes to use, including commercially, under the licence. Conformance is more precise: an implementation may be “inspired by,” “implement elements of,” or “conform to” a named version — and only the last is a conformance claim, always made against a specific version. See Open Architecture.

Evidence, limitations and honesty
Is it based on established research? What is original, and what is synthesised?

It is derived from a documented literature landscape spanning knowledge engineering, knowledge management, epistemology, records and archival governance, information systems and AI. The underlying principles have deep histories; the reference architecture is an original synthesis of them. See the Literature Landscape.

Has it been tested in practice? What does the worked example show — and not show?

The architecture is complete and internally consistent, but it has not yet been validated on a real institutional case. The worked example demonstrates that the full lifecycle hangs together on one governed decision; it does not prove the architecture works in the world. We say “designed to,” not “guaranteed to.”

What would validate it, and what are its current limitations?

Documented applications in real settings — recording what the architecture helped with, where it created unnecessary burden, which concepts proved ambiguous, and what had to change. Until then, parts marked “Draft for Experiment” are hypotheses, not settled findings.

Could governance entrench institutional bias, or suppress dissent?

It could, if authority were treated as a substitute for evidence — so the discipline treats it as the opposite. Acceptance requires justification, supersession keeps lineage, and superseded or minority positions are retained rather than erased. Governance is meant to make authority accountable and reversible, not final — and this is exactly the failure the architecture must keep being tested against.

Can a well-governed knowledge object still be wrong?

Yes. Governance improves warrant — how well a claim is justified, sourced and accountable — not truth itself. A well-governed claim can still be mistaken. The point is that when it is, you can trace how it came to be relied upon and revise it under control, rather than discovering an untraceable error.

Can provenance and metadata create a false impression of reliability?

Yes, and naming that risk matters. Provenance shows where a claim came from, not that it is correct; assurance can be theatre if it is not honest. The discipline guards against this by tying reliance to justification and accountable acceptance — not to the mere presence of metadata — and by holding its own claims to the same standard.

Why can’t existing document-management systems already do this?

They manage files, versions and permissions — not warrant. They can tell you who edited a document and when, but not why a claim should be believed, who is accountable for relying on it, or whether it still holds. Knowledge Foundry governs the claim; document management governs the container.

About

A discipline, derived from evidence.

Knowledge Foundry did not begin with a product. It began with a question — how does knowledge stay trustworthy as it moves between people, institutions and machines? — and a structured review of the traditions that have each answered part of it.

Where it comes from

The discipline is derived from a literature landscape spanning knowledge engineering, knowledge management, records and archival governance, and AI. Its principles are the obligations that evidence makes unavoidable.

Where it is going

Today, Knowledge Foundry is an open discipline and reference architecture, studied and applied by professional associations and educational institutions. It may be instantiated through many kinds of governed knowledge systems; implementations are expected to vary by domain, institution and technology.

Honest status

This is serious, in-progress work. The architecture is complete and internally consistent; parts of it await validation on a real institutional case before they are considered settled. We say “designed to,” not “guaranteed to.” The discipline is about warranted claims — so we hold our own to the same standard.

Who stewards this

Knowledge Foundry is edited and stewarded by its founding editor — [ add your name ]. Authority over what is accepted into the architecture is attributable, as the discipline itself requires; as the work matures, stewardship may broaden to a named review group.

How it was made

The reference architecture is an original synthesis derived from the literature landscape. Drafting and editorial development were assisted by AI tools; the architectural claims, and every decision to accept them, are the editor's own. The discipline is about warranted, attributable knowledge — so we say plainly how this was made.

Citing and reusing

Everything is free to read and openly licensed. See Open Architecture for the licence, stewardship and conformance terms, and how to cite the work.

Get in touch

Start a conversation

If this is the work you’re trying to do, get in touch.

Whether you want to apply the architecture, teach or research with it, contribute evidence from real use, or explore working together — the useful conversations begin with a specific problem.

Emailhello@knowledgefoundry.org
Enquiries fromAssociations · Institutions · Researchers · Practitioners · Learners

We answer every letter that names a real problem.