Net benefit, farm to table.
"Fine — one act, one reward. But a real economy is a supply chain a thousand hands long. How do you account for all of it?" Fair question. Let's answer it the hard way: follow one loaf of bread through the whole system, hop by hop, record by record.
MethodHow to read this page
The mechanics here — what gets recorded, when, and why — come from the Copiosis project's published answer to exactly this question, plus the system's core rules about goods and rewards. The bread trace itself is our illustration: a concrete walk-through built on those rules, with illustrative numbers, showing how they compose over a real chain. Where the design leaves something open, we say so.
One correction to carry in from the start: in Copiosis, "available at no cost" does not mean "free-for-all." Nobody walks out of a store with unrecorded goods. Every handoff is a recorded property transfer — and that single fact is what makes whole-chain accounting possible.
The head startThe tracking system already exists
The objection imagines Copiosis must invent an all-seeing accounting machine. It doesn't — because money economies already built one. When you buy a head of lettuce today, point-of-sale software decrements the grocer's inventory, triggers a reorder threshold, notifies a wholesaler, and feeds a demand forecast. Modern logistics tracks every pallet, every hop, every timestamp, up and down the chain, and does it so well that "just-in-time" delivery is boring.
Instantaneous demand
Consumption is visible the moment it happens — what's moving, where, at what rate, for any product, luxury or necessity.
Inventory, anywhere
How much of anything exists, where it sits, what's in production, and what's in transit — queryable at any time by producers and coordinators.
Predictive demand
Historic patterns, seasonality, weather, events — the same forecasting grocers use to stock winter coffee lids predicts tomorrow's bread demand.
Copiosis's claim is deliberately modest: repurpose these rails, don't replace them. Keep the barcodes, the inventory software, the logistics networks. Change only what the records are for — instead of settling payments between links, they feed the net-benefit calculation. One thing is added: alongside demand data, producers see an estimate of net benefit for what they're considering making, so they can tell in advance how a decision would affect their reward.
The inversionThe one big difference: value doesn't flow through the chain
Here's the structural move that makes chain accounting simpler than today's, not harder. In a money economy, value travels backward through the chain: the grocer pays the distributor, who pays the baker, who pays the miller, who pays the farmer. Every link must price its output above its input — margins stack, costs cascade, and each handoff is a negotiation, an invoice, and an opportunity for dispute.
Goods flow forward, money flows backward
Each link is paid by the next link. Your reward depends on your buyer's margin, your negotiating leverage, and how much cost you can push onto someone who isn't at the table.
Goods flow forward, rewards don't flow at all
No link pays any other link — ever. Goods move forward leaving records; when benefit lands, each contributor is rewarded directly and independently by the algorithm, sized to their own contribution.
Why is nothing owed between links? Because of the system's three kinds of goods. The farmer's tractor, the miller's wheat, the baker's flour, the distributor's truck — inputs used to produce for others are capital goods, provided at no cost to recognized producers. The farmer doesn't buy seed; the baker doesn't buy flour. Each simply receives inputs (recorded), adds their contribution (recorded), and passes the result on (recorded).
This deletes entire categories of supply-chain difficulty in one stroke: no double-marginalization, no invoice fraud, no cash-flow squeeze bankrupting the smallest link, no cost-shifting to whoever has the least leverage. What remains is exactly one problem — who contributed what to the final benefit — which is the problem the algorithm exists to answer.
The traceOne loaf of bread, hop by hop
Follow the loaf. At every hop, ask two questions: what moved? and what got recorded? Six hops, six records — each one an entry today's inventory systems already know how to make.
The farmer grows wheat
Seed, equipment, and fuel arrive as capital goods at no cost — each delivery a recorded transfer into the farm's stewardship. The farmer grows and harvests the crop. The grain doesn't belong to nobody; it's the farmer's output, in her possession, until it moves.
Grain becomes flour
The grain transfers from farm to mill — a recorded change of possession, no payment attached. The miller's contribution is transformation: cleaning, grinding, grading. Output: flour, attributed to the mill, carrying its input history with it.
Flour becomes bread
Flour, yeast, salt, and oven-power arrive as recorded producer inputs. The baker's craft turns them into 400 loaves before dawn. Each batch is attributable: these loaves, this baker, this flour, that field.
Bread moves to the store
A driver carries the morning's loaves to three neighborhood groceries. Transport is a contribution like any other — the benefit of bread being where people are — and it has its own footprint, which will land on the driver's own calculation, not be smuggled into a "delivery fee."
The grocer stocks the shelf
The grocer receives the loaves (recorded), keeps them fresh, findable, and available at sensible hours. Retail's contribution is real: availability, curation, waste management. Inventory software watches the shelf exactly as it does today.
A family checks out a loaf — and the loop closes
Bread is a necessity, so the family owes nothing. But they don't vanish into the night with it — they check it out, and the system records the final property transfer: this loaf, this household. If it were a luxury (say, the bakery's saffron brioche), the consumer's NBR would be destroyed at this same moment — not paid to anyone — and the record made would be identical in kind.
The payoutNow the rewards — computed, not negotiated
Benefit has landed: a family is fed. Nutrition happens, satisfaction gets reported, and the algorithm now runs once per contributor — not once for the chain. Each person's inputs are their own: their resource use, their reach, their measured contribution to the outcome, their harms. Here's the shape of it for our loaf, with illustrative numbers (coefficients at 1, magnitudes invented; the structure is the point):
| Contributor | What the algorithm sees | Illustrative reward flow |
|---|---|---|
| Farmer | Fed thousands via many chains; regenerative soil practice lifts her environmental term; her wheat is in every downstream loaf | Large, ongoing — aggregated across every loaf her grain reaches |
| Miller | High-volume transformation, modest energy footprint, many beneficiaries per producer | Steady, ongoing |
| Baker | 400 households fed daily; strong satisfaction reports; small energy harm subtracted | Strong, daily |
| Driver | Availability benefit across three stores; fuel burned counts against — an electric van would literally raise his reward | Modest, per delivery day |
| Grocer | Access and freshness for the neighborhood; spoilage subtracts; accurate stocking shows up as benefit | Steady, ongoing |
| The family | Nothing owed. Their honest satisfaction report is itself a small net-beneficial act | A small NBR trickle — for closing the loop |
Three properties of this payout are worth slowing down for:
- Rewards persist as long as benefit persists. The farmer isn't paid once at the farm gate and forgotten; as her grain keeps feeding people, her reward keeps arriving. Contribution to durable good is an income stream, not a transaction.
- Nobody's reward depends on anyone else's margin. The driver isn't squeezed because the grocer had a bad quarter. Each calculation is independent — the chain shares an outcome, not a pot.
- The consumer is data, not a wallet. What the family reports and what measurably happens to them (the satisfaction and benefit terms of the formula) feeds every contributor's calculation upstream.
HarmExternalities, decomposed to whoever caused them
Here's something a price fundamentally cannot do. The retail price of today's loaf blends every cost and every harm in the chain into one opaque number — the pesticide runoff, the diesel, the packaging waste, all averaged into $3.49 and charged to someone who caused none of them. The chain's harms are socialized; its profits are not.
In the traced loaf, each harm lands on the actor who caused it, inside their own calculation:
Field-level harms
Pesticide load, water draw, soil depletion — subtracted from her environmental term. Switch to regenerative practice and her number rises; nobody else's changes.
Road-level harms
Emissions per route are his, not the baker's. The cleanest route and vehicle are, for the first time, directly and personally profitable.
Production harms
Oven energy and any waste stream subtract from the bakery's own reward — an always-on efficiency incentive no energy audit ever matched.
Waste harms
Spoiled loaves are measured harm on the store's number — overstocking stops being a marketing strategy and starts being a visible cost to the person who chose it.
Coordination"But without prices, how do they know how much to make?"
The standard economics objection says prices are the signal, so no prices means no coordination. But look at what the trace actually produced: a live record of consumption (hop 6), inventory levels at every node (hops 1–5), and predictive models on top. That is the signal — the same one today's logistics runs on. Prices are a lossy, laggy proxy for exactly this data; the chain that has the data doesn't miss the proxy.
- The grocer sees bread velocity per shelf, per day, and requests inventory accordingly — precisely as today, minus purchase orders.
- The baker sees demand across her stores plus the forecast (holiday spike incoming), and sees the estimated net benefit of baking 60 more loaves versus a new pastry line — before firing the ovens.
- The farmer sees regional flour draw-down and projected planting needs a season ahead — better information than commodity futures give her today, because it's demand data, not speculation about demand data.
- Surpluses announce themselves. Overproduction shows up as inventory that isn't moving and spoilage charged to someone's number — a self-correcting signal with a name attached, instead of a mystery warehouse of unsold goods.
Being honestWhat's genuinely hard here
A worked example can make anything look tidy. Three open problems deserve naming, because they're where the real engineering lives:
The attribution problem. The records tell you who touched the loaf; deciding how much of the final benefit each touch caused is a judgment the algorithm structures but doesn't eliminate. How much of a loaf's goodness is the farmer's grain versus the baker's craft? The project's own answer is candid: valuation is a living process, refined case by case — "more art than science" — with the open coefficient-and-jury machinery there to keep the judgments visible and revisable.
The boundary problem. Chains don't end — the mechanic who fixed the tractor contributed, and so did whoever taught the baker. A workable system needs a horizon where contribution tracking stops, and any horizon is arguable. (Persistent rewards soften this — the teacher's own teaching acts carry their own ongoing streams — but the line-drawing is real.)
The data problem. "Repurpose existing rails" is honest for barcoded retail chains in developed economies. It's aspirational for informal markets, smallholder farms, and services with no point-of-sale trail. Coverage would be uneven for a long time, and the design has to tolerate gaps rather than assume omniscience.
Keep exploringRelated reading
The Formula, Annotated
The calculation each contributor's records feed — every variable, every dial, worked by hand.
Read this →Can It Be Gamed?
The six-vector security review of the same record-and-reward machinery this trace runs on.
Read this →The Three Kinds of Things
Necessities, luxuries, capital goods — the classification doing the load-bearing work at every hop.
Read this →See the whole system at street level
You've followed a loaf through the economy. Now follow a person through a day — and watch these same mechanics from the inside.
A day in CopiosisBack to Deep Dive