Thesis

A knowledge base of notes whose links are explained when written can be mapped by computation, and AI is then only needed to interpret

Info

Originally written in French. Translated by AI — the meaning has been preserved, not the prose.

Angle

When every link in a knowledge base of notes carries a sentence that explains the relation, the structure of the base is already written: a script turns it into a graph in a fraction of a second, with no model, and a model is then only needed for the steps that require interpretation. The judgment was paid for at writing time, link by link; the computation merely makes it visible, and the resulting map is worth exactly what the written links are worth — flaws included.

Synthesis

Taken one by one, these notes talk about a tool, a cost criterion, a structural effect, a use of paths. Together, they describe a shift in where AI is needed. Usually, you ask it to read documents to infer the relations, then you explore the result. Here, the inference has already happened at the moment each link was laid down and justified; redoing it would cost tokens for a result that is less faithful and varies from one run to the next.

That shift has two consequences that hold together. The first is economic: what is left to hand to a model shrinks to interpretation — naming groups, judging a path. The second is epistemic: the graph fixes nothing. A note without links stays isolated, a link without an explanation becomes a silent relation, and an overly heavy navigation structure draws the library in place of the ideas. The map becomes an instrument for checking the knowledge base rather than an addition of knowledge.

Tensions / contradictions

The gain assumes a cost already paid elsewhere: explaining every link is work, done by hand or validated at the moment an AI ingests the source. The thesis does not say that AI disappears, it says that AI has already done its job, and that there is no point paying for it twice.

Navigation nodes pull the other way: useful to the reader, they distort the split into groups and the paths. A knowledge base well written for reading is not automatically well formed for computation.

Questions

  • Does a knowledge base whose links were laid down by an AI inherit that AI's biases in its graph, and how do you tell them apart from the real structure of the domain?
  • Should navigation nodes be marked so they can be excluded from the computation, at the risk of isolating the notes they alone connected?