Ownership, in practice

Saying material is “owned” means little if there is no way to walk away with it. Every one of the six tools writes to a plain, inspectable backup on a schedule the person sets, and that backup is not a proprietary format held hostage by the software that produced it — it is meant to be readable, exportable, and usable even if this particular installation were switched off tomorrow.

This is also where the separation between the six rooms pays its clearest dividend. Because each tool keeps its own account of what it holds, a backup of the knowledge base can be restored, inspected or moved without dragging the graph, the workflow history or the agent configurations along with it whether they are wanted or not. Ownership, here, is not one giant undifferentiated export — it is six smaller, legible ones.

Fig. 6.1 — Six rooms under one roof, each keeping its own honest account — and each recoverable on its own, without needing the others.

That figure is also, quietly, a picture of the entire book: six strong, separate tools, sharing an address and an owner, each one answerable for what it holds. Nothing about that arrangement was a shortcut. It was the version of the system worth building carefully before asking whether — and how — the rooms should ever start talking to each other.