Organisations do not have a document problem

"Where is that file?" is the question organisations think they have. It is not the real one.

The real question is harder: what do we currently know, what do we merely assume, what have we already decided, and on what evidence? That answer does not live in a folder. It is distributed across inboxes, chat threads, meeting notes, systems, processes and individual memory — and it decays quietly.

A knowledge-state problem

Knowledge state is the current, governed position of an organisation on the things that matter: claims it treats as authoritative, assumptions it has not yet validated, decisions it has taken, and the evidence behind each. Documents are inputs to that state. They are not the state itself.

Treating the two as the same thing is why search-heavy tooling disappoints. Better retrieval over an ungoverned pile still returns fragments, not positions.

What changes when state is explicit

• A new team member reads the current position instead of reconstructing it.
• A decision carries its rationale and the sources that supported it.
• An assumption is visibly an assumption until someone validates it.
• Superseded positions remain readable, so history is reconstructable rather than overwritten.

Capture is not commitment

The discipline that makes this work is a boundary between capturing a source and changing what the organisation holds as true. A captured note, transcript or link is provenance. It becomes part of authoritative state only through an explicit, reviewed commit.

That single boundary is what separates knowledge infrastructure from storage.