Seednote
Economic Distance
A processor eighty miles away can be more practical than one fifty miles away. Economic distance is derived from geography, logistics, infrastructure, cost, timing and constraints, which raises the question of whether it is a better primitive than location.
Wellzai2 min read
On a map, fifty miles is closer than eighty. In a supply network it may not be. Wellzai's formation design uses exactly that illustration: a processor eighty miles away can be more practical than one fifty miles away when transportation routes, infrastructure, service patterns, capacity, timing or economics differ.
The design calls the difference economic distance, and it is careful about what kind of thing that is. A location is a fact about a place. Economic distance is derived intelligence: geography combined with logistics, infrastructure, cost, timing, constraints and operating conditions. It matters most when a configuration is being discovered and its viability judged. Its neighbours in the design sharpen the point. A required geography is a hard constraint; it eliminates arrangements that cannot meet it. A preferred distance is a soft one; it shapes desirability and can be traded against other things. Economic distance fits neither list cleanly. It is closer to a measure of how hard it is to make two capabilities work together.
The implication is that "nearby" is not something a formation system can read off a map. It has to be worked out against a particular intent, and the answer can change when timing or capacity does.
The open question is whether it deserves to be more than a calculation. In RSM, a place is a canonical reference; anything computed from it is derived, carries its inputs, and is never canonical fact. The precise locations economic distance would be computed from are themselves governed, disclosed only for a purpose. Is economic distance a better primitive than location for reasoning about regenerative supply, or does it only make sense as a judgement recomputed each time someone asks?