Originally written in French. Translated by AI — the meaning has been preserved, not the prose.
Angle
A filing plan reveals its real criterion only when an object turns up that it wasn't drawn for: as long as the objects are the ones used to build it, two incompatible criteria — the subject a document talks about and the function it performs — give the same filing, and nobody needs to know which one they are applying. A translation guide, which talks about a book without being part of it and which governs the translations to come, separates the two answers and forces a choice. The definition that comes out of it isn't the one you thought you held: a stable zone isn't the zone of what moves little, it is the zone of what durably governs.
Synthesis
The movement reads in four steps, and each one corrects the previous.
The first is a filing criterion applied without having been chosen. Filing by subject works so well on anticipated objects that it passes for obvious, and it turns out to be wrong at the first document that talks about a piece of work without being part of it.
The second is a definition that discovers itself insufficient. Describing a workspace's zones by their rate of change is convenient, explains a lot, and says nothing about a file's function — a rule validated yesterday governs just as much as a rule laid down six months ago.
The third is the price of the correction. An architecture can absorb the case through an exception, which costs little and teaches nothing, or draw a reusable criterion from it, which forces the reopening of a settled definition. The second path is the only one that makes decidable the cases not yet met — and that is why the measure of an architecture isn't the number of filled slots but its capacity to file an unforeseen object.
The fourth is the agent of the trigger, and it is the most counter-intuitive. An assistant has understood nothing more: it applies to a new object distinctions already written down, without weighting them by habit. What it produces isn't a discovery, it is discomfort — and discomfort forces you to state the rule you were keeping tacit. The gap brought to light doesn't separate the machine from the human, it separates the written definition from the definition actually practised.
Tensions / contradictions
Two filing criteria coexist without agreeing. The rate-of-change reading, laid down to prevent the current state being written in among the permanent rules, keeps its function as a guardrail; the function reading contradicts it on borderline cases, since it admits into the governing zone a file that is still moving. Neither fully replaces the other: the first protects against a frequent confusion, the second settles the cases the first can't settle.
A second tension runs through the notes about the assistant. Its value lies in its applying the system without habit — and that is also what makes it fallible, since the same literal application sometimes produces an absurd filing, in a rigorously identical form.
Questions
- What signal warns that an unforeseen object has just been filed out of habit, without the criterion having been laid down?
- Can an architecture keep correcting itself this way indefinitely, or is there a point where the accumulation of revised definitions makes the system unexplainable to a newcomer?