Why food needs a protocol

Every food system in history has failed to interoperate. Not because the people building them were careless, but because each one invented its own data model. A supermarket's stock system cannot read a smallholder's harvest log. A restaurant's menu cannot read the mill's certification. A charity's collection round cannot read the bakery's surplus.

So the industry does what it always does. It adds an integration. Then another. Then a platform to manage the integrations, and a fee to sit in the middle of them.

The smaller primitive

FoodBlock compresses the entire domain into three fields.

{
  "type":  "what it is",
  "state": "its properties",
  "refs":  "what it connects to"
}

That is the whole thing. A farmer is a block. Their tomatoes are a block. A purchase is a block. A review is a block. Each one is hashed, signed by whoever made the claim, and linked to what came before it.

The compression is what makes universal adoption viable for the first time. A protocol rigorous enough for a multinational supply chain is also simple enough that a reasoning model can write a valid block from a sentence of plain English.

Why this matters now

Three reversals are in flight at once. Precision agriculture robotics. AI-run intensive production at garage and rooftop scale. And chain-anchored protocols that let strangers agree on a shared record with nobody in the middle.

Together they make small-scale, local, regenerative production economically competitive with industrial monoculture for the first time in 150 years.

Food is the most repeated transaction in human life. Roughly 1,100 decisions per person per year. A protocol that gets food right does not disrupt one industry. It rewires how a civilisation relates to its most fundamental category.

This is a twenty year frame, not a quarterly one.