ECOSYSTEM
Two axes describe the whole system: scope — how wide a window an instance has — and depth — how far a task decomposes. Lessons move on the first; your data stays on the second.
Scope is the width of a window. A wider window is the same role with more context, not a new role. This is the axis that shared lessons and standards travel across.
Depth is how far a single task decomposes — workflow, to sub-modules, to the leaf work. This axis carries your operational data, which never leaves your own line.
The rule that keeps the two straight: lessons move on the scope axis; data stays on the depth axis.
Each instance is an independent user — its own vault, its own data. But what any instance learns about how to work is distilled upward and shared across the network. A standard authored once is available to everyone; a lesson learned in one place prevents the same mistake everywhere else.
The result is a network whose capability grows with the number of users, not despite it. Users contribute to the growth and betterment of the system as a whole — that is the ecosystem, and it is the product.
What crosses the network is distilled lessons and standards, never your context or your private data. Your vault is your second brain; only the reusable lessons leave it.
Stand up your own instance and start contributing lessons to the network.