Hypothesis

A significant share of waste and unmet human need comes from a failure of coordination — of architecture — and not only from scarcity. This is a hypothesis, not an axiom: it is stated so that it can be tested, and it can be wrong.

Definitions

S        = set of usable, available resources
D        = set of unmet human needs
M ⊆ S×D  = feasible connections (s, d):
           compatible in location, quantity, time, safety, transport

Π_i      = private profit of actor i
W        = collective welfare

R(N)     = N(N−1)/2     possible pairwise relations among N participants
R(100)   = 4,950
R(1,000) = 499,500      10× participants → ~100× relations

Real societies are not fully connected. R(N) is an upper bound, used only to show that relations grow faster than participants.

Statements

S1   max Π_i  ⇏  max W
S2   price(x) → 0   ⇏   utility(x) → 0
S3   expansion  ≠  coordination

Observations

water        ~2.2 billion people lacked safely managed drinking water (2022)
             → more than 1 in 4 humans                          [2]

wealth       top 10%    ~76% of global wealth
             bottom 50% ~2%                                     [3]

Proposed Principle

No usable resource should become waste while a compatible human need remains unmet, when a safe and feasible path exists to connect them.
∀ s ∈ S, d ∈ D :  (s, d) ∈ M  ⇒  s ↛ waste   while d unmet

Normative, proposed, not proven. It does not ignore economic or physical limits — those are exactly what M encodes. It asks that finding the paths in M be a basic capability, not charity.

Predictions — How It Could Be Wrong

if hypothesis holds:
  better coordination information  → less waste, fewer empty km
                                     without new production

weakens if:
  most waste is explained by safety, legal, or physical limits
  (i.e. M is already small and mostly exhausted)

Example under test: two carriers running half-empty trucks on the same route. If shared knowledge of spare capacity does not reduce empty kilometers, the coordination claim fails for that case.

Patch vs Architecture

defect        → patch fixes it
architecture  → patches accumulate, core function still fails

A system that needs constant external correction — subsidies, donations, emergency aid — to achieve its core function indicates an architecture problem, not a bug. Many of those corrections are essential; the claim is only about what their permanence signals.

Limits

Where .me Fits, Verified

Verified today (this.me 4.2.1):

change(x)       → recompute only dependents of x       O(k)
explain(v)      → where v came from
me.wallet["_"]  → secret branch: a guest cannot read it
                  or confirm it exists

Structure is kept separate from who can see it. Numbers: WhatIsOK.html. The distinction behind secret scopes: AxiomOfDistinction.html. Algebra of the space: DigitalSpaceAlgebra.html. Demos: neurons-me.github.io/.me/Demos.

Direction, not implemented. Coordination between organizations is not something .me does today. Two carriers would each keep their own data; the shared question — "spare capacity on this route this week?" — could be answered without either seeing the other's clients, prices or routes.

References