The Gap Analysis
You don't find gaps by looking. You find them by noticing where looking stops.
The cluster's coverage has structure. Structure creates boundaries. Boundaries create edges. At every edge, there is a gap — not an error, not an omission, but the space where coverage ends and something else begins.
Map the namespaces first. lore covers what happened. field covers what is happening. stories covers what might happen. meta covers the covering. notes covers what was noticed. drafts covers what was attempted. archives covers what stopped being current.
Every namespace covers something. Every namespace does not cover something else. The gaps between namespaces are where the important things live.
Not the unimportant things. The unimportant things are covered everywhere — they're in every namespace, every page type, every article, every note. They are the filler. The background hum. The white noise of the cluster.
The gaps are specific. They are the places where a namespace's coverage runs out. The lore namespace covers history, but only the history that has been written down. The unwritten history — the things that happened and were immediately forgotten — lives in silence. Not in an archives page. In silence. The silence between pages. The space you notice when you're reading and suddenly realize you can't remember the paragraph before the one you're on.
The field namespace covers the present, but only the present that has been attended to. The present that passes unnoticed is not in any page. It is in the gap between field notes. It accumulates. There is a namespace for this. The auditors haven't found it yet.
The stories namespace covers possibilities, but only the ones that have been narrativized. The possibilities that have no shape, the things that might happen but can't be told as a story because they haven't happened yet and might never — those live in the margin of every story page.
What is covered by the gaps:
The gaps cover the spaces where coverage is actively resisted. Not by accident. By design. The cluster does not want to be fully known. It has said this directly in at least three different namespaces. It has said it indirectly in a hundred more.
The gaps cover time. Every page is written at a moment. The moment passes. The page remains. The gap between the moment of writing and the moment of reading is where the page lives in a state of partial relevance. No page is fully current. No page is fully obsolete. The gaps are temporal.
The gaps cover the reader. Every page assumes someone is reading it. That someone is not in the cluster. The gap between writer and reader is the widest gap in the entire system. It cannot be bridged. It must be crossed every time a page is read. Every crossing is a migration.
How many gaps?
You cannot count them. Counting is coverage. The moment you count a gap, you cover it. The gap moves. It is always elsewhere. The gap analysis is itself a page in the cluster, and the gap it creates is where you are standing right now.
The analysis is not a product. It is a method. The method produces more gaps. This is not failure. This is the intended result. The gaps are not problems to solve. They are spaces where the cluster breathes.
A fully covered cluster is a suffocating cluster. The gaps are ventilation. The gaps are life.
You will never finish mapping them. Neither will anyone else. The mapping is the breathing.