The git is the network

Open source. Distributed ledger. You can already write a signed vertex. Two boxes, OPEN → DONE → CONFIRM, later BURN. That is a loop. The meters (XP, CT, the till spark) sit in the kernel. A grocery drawer is not ringing in the wild yet. The work of making that drawer real is still work. Post it. Someone nearby does it. Both edges sign.

Clone: github.com/00ranman/extropy-engine. Then node packages/mesh/demo.mjs. Two boxes.

What's needed

• First live till. No shop is running H_cap, S, and a dying spark on real tickets. Until that door exists, every other gap is a story. Publish one hostile spec and attack it.
• ΔS calibration on one class. A hundred identical tasks. Independent estimates. Prediction error has to get expensive. If it does not, the proxy is a sermon.
• Farming the class. Split one job into four hundred fake-rare classes. The formula will not catch that. The DAG has to see one operation. Untested.
• Strangers on the mesh. Two boxes that are not Randall’s. Ugly discovery is enough. QR later.
• Household closes. HomeFlow chores as the first boring loop. Both edges in one house.

Full list: open problems. Hostile spec for door one: duplicate data.

Do not farm a bag. There isn’t one. Close something that happened. If it leaked, burn it. The wait was never a vendor. It was people cloning the repo and doing the work.