Originally written in French. Translated by AI — the meaning has been preserved, not the prose.
Angle
A context engine that runs on its author's machine forces the AI to work after collection, on what was brought back. Porting it onto an assistant reachable from a phone does not make it a portable version of the same tool: it changes when the AI steps in, and therefore what it can still modify. At a trade show, an ingestion run between two stands points out the unasked questions while the people are still there; the same analysis done after the fact can only work on a closed collection. The gain from the port is not mobility, it is that the information brought back stops being final at the moment you bring it back.
Synthesis
The move is not decided on features but on a dependency. As long as the engine assumes a machine that is powered on, connected and reachable, its mobility is conditional, and its conditions are out of reach while travelling. Removing the machine then becomes the goal, and the port reduces to an inventory: three functions — reasoning, applying rules, remembering — of which a consumer assistant already supplies two. Only the memory was missing, and a spreadsheet is enough to supply it.
What the platform provides, it provides on its own terms, and those terms shape the architecture more surely than any plan. A size cap on the instructions cuts the rules into an embedded core and an extension loaded on demand. The cost of resolving identifiers decides that a context will be a single tabbed workbook rather than a collection of documents. Access latency makes it necessary to hold the workbook's identifier for the duration of the conversation. None of these decisions comes from a design intention: each one is the trace of a constraint that was hit.
Once the system is reachable while walking, capture changes regime — you dictate, you persist, without deciding anything — and that is precisely what makes the separation between keeping and qualifying indispensable. The pace of collection does not forgive a system where everything coming in would immediately become knowledge: the speed gained at capture would be paid for in a confirmation loop at ingestion. The resulting mode remains inferior to the original engine on almost everything, and is justified by the single constraint it lifts.
Tensions / contradictions
Two requirements pull in opposite directions. Collection on the move wants a single, immediate gesture; protection against the confirmation loop wants two gestures separated in time. The article reconciles them by placing the separation in the system rather than in the operator's hand, but the reconciliation only holds if ingestion actually happens — a stock persisted and never ingested reproduces exactly the problem the separation was meant to avoid.
A second tension sets mobility against the regime of use: the nomadic mode is claimed as complementary, while the material collected in the field is what will then have to be processed by the full engine, with no description of how you move from one to the other.
Questions
- What, in a dense day in the field, would trigger ingestion at the right moment, given that the stock of persisted sources asks for nothing of its own accord?
- How does material produced in the nomadic mode reach the full engine without being re-entered?
- Does an architecture entirely deduced from platform constraints survive the disappearance of those constraints, or does it have to be redone every time a cap moves?