7products
shipping code
AssetShop
Everything below is
checkable in one command.
Seven products with shipping code. Eight proof objects that recompute from their own artifacts. Two published standards. This file has no dependencies, makes no network calls, and works offline. Read it in ten minutes, verify it in one.
What exists.
Measured from the shipped artifacts, not quoted from a document. Function counts come from the files themselves.
| Product | What it does | Size | Functions |
|---|---|---|---|
| Recipes For Ingredients | Cook from what you already have | 1,264K | 351 |
| EOS, demonstrated | The enterprise decision layer, shown not described | 517K | 211 |
| SecureLive | End-to-end encrypted video in the browser, no plugin | 413K | 166 |
| Nexus Search | Search across the estate | 250K | 109 |
| VoxChain | Voice and audio rights management | 243K | 120 |
| VideoChain | Video publishing | 179K | 83 |
| DApp Network | The application network | 184K | 29 |
8proof objects
all recompute
all recompute
29realms
built
built
82executables parsed
0 broken
0 broken
How to check it.
A proof object carries a value, the SHA-256 of the artifact it describes, the rule that produced it, and the command that recomputes it. If the artifact changes, the proof fails. That is the point.
tar -xf ASSETSHOP_EOS_R147_COMPANY_PACKAGE.tar.gz
cd ASSETSHOP_EOS_R147
./ship.sh
# any single figure in the table above, checked on its own:
node TOOLS/proof.mjs verify \
36_DEPLOY/IPFS_WEB3_LIFESTYLE/recipes/proof.json \
36_DEPLOY/IPFS_WEB3_LIFESTYLE/recipes/index.html
Ten checks, one answer, no account, no network. It refuses to report success if any post-condition fails.
| Check | What it proves |
|---|---|
| toolchain | 82 executables parse; nothing was silently corrupted |
| release gate | 0 P0 findings across 80 pages |
| canonical nav | one block hash across 75 pages, byte-identical |
| post-conditions | every file still parses after every change |
| proof objects | all 8 recompute from their artifacts |
| server source | none in the content-addressed mirror, which cannot be unpublished |
Two standards, published openly.
CC BY 4.0The Verify Standard
Five requirements for a claim a stranger can rerun without the vendor. Current level V3: the harness is published unauthenticated and runs offline.
CC BY 4.0The Guard Standard
Five levels for keeping an AI-operated codebase honest. Blast radius, post conditions, idempotency, self-verifying checks, typed operations. Currently G4, with G5 published as PARTIAL rather than rounded up.
Why openAdoption is the moat
Conformance requires publishing your failures. Most vendors will not pay that cost. The ones who do become peers in a category we named, and the author is the reference implementation by default.
The thesis, in one paragraph.
Every vertical here is the same problem: two authoritative sources describe one object and disagree, somebody finds it late by hand, and nobody owns the layer above them. Purchase order against invoice. Royalty statement against distributor. Title against tax assessment. Seats purchased against seats used. The engine that resolves it does not know what a purchase order is. Swap the adapters and it reconciles royalties. That is why this is one engine with many applications rather than a portfolio of unrelated products.