Value Stories
How per-unit custody creates value. Each story is an intent flow: a scenario triggers an intention, actions produce artifacts, outcomes prove value.
Can operators walk the object?
A beekeeper with a phone, a hive, and no crypto knowledge. Onboarding is the binding constraint.
A beekeeper stands at a hive with a phone. The hive has never touched a chain. Registering it on existing platforms takes forms, a wallet, a seed phrase, and a support ticket.
Register the hive as an object in under five minutes, zero crypto knowledge.
Operator walks away with a registered hive object and a QR code for that hive, in under 5 minutes, via phone.
Registration requires wallet install. Hive object not visible on chain. GPS coordinates not signed into the object. Operator needs support ticket to complete.
Can every hand sign?
The lab signs directly onto the batch. The attestation lives on the object. No paper, no PDF, no trust broker.
A lab tests a honey batch for UMF grade. On paper this takes days to reach the producer and weeks to reach the buyer. The test result travels by email and PDF.
Sign the lab result directly onto the batch object as an attestation.
Lab attestation appears on the batch object within 60 seconds of test completion. Signed by lab key. Visible to the next owner in the chain.
Attestation written by producer instead of lab. Attestation not cryptographically signed. Lab key shared or stored unsafely. Result rewritable after signing.
Does the split stay atomic?
One batch consumes in a single PTB. N jar objects emerge. Each carries the full chain back to the hive.
A processor takes a 500kg batch and splits it into 2500 jars. On existing systems, provenance averages over the batch and dilutes per jar. One compromised unit poisons the whole batch.
Split the batch object into 2500 jar objects in a single atomic PTB, each carrying the full custody chain.
Batch object consumed. 2500 jar objects created. Each jar points back to the same batch, hive, and lab attestation. Split completes in a single transaction.
Batch object persists after split. Jars created with missing parent references. Split requires more than one transaction. Partial split leaves orphaned jars.
Can the buyer prove it without asking?
Scan the lid. Walk the chain backward. No login, no permission, no brand in the middle.
A buyer stands in front of a jar on a Tokyo shelf. The label says manuka. The price is two hundred dollars. The buyer has no way to verify.
Scan the QR and see the full chain — hive, harvest, lab, processor, export, shelf — in under three seconds.
Scan resolves in under 3 seconds. Every owner visible. Every transfer timestamped. Every attestation signed. No login required.
Scan requires wallet install or sign-in. Chain shows gaps. Timestamps out of order. Attestations missing signatures. Latency exceeds 3 seconds.
A researcher wants to trace a jar backward through every owner without asking permission from the brand. On existing systems, supply chain data is private, fragmented, or only available after a FOIA request.
Walk backward from the jar to every prior owner, attestation, and event, without requesting access.
Full chain visible from any object in the history. Read-only. No permission required. Backward walk returns in under 2 seconds.
Backward walk blocked by access control. History shows only the current owner. Events hidden or redacted. Walk returns partial data.
Zero walked jars on testnet after 30 days. OR operator registration requires more than 10 CLI commands. OR scan latency exceeds 3 seconds. Any one kills the pattern.
Who this is for
| Who | Job | Switching trigger |
|---|---|---|
| Beekeeper | Register source, sign harvest, defend the claim | Phone-first onboarding, no wallet, no seed phrase |
| Lab | Sign attestations directly onto the batch | Lab key storage, one signing flow, zero PDF email |
| Processor | Split batch atomically into N jar objects | One PTB, full chain inherited by every jar |
| Buyer | Audit backward without asking permission | Scan resolves chain in <3s, no login required |
Questions
If one walked jar proves the pattern for manuka, what's the next unit that inherits it — and which patterns don't transfer?
- Is manuka the right first category, or does the niche premium distort what we learn about onboarding?
- The split PTB prevents partial batches — but what happens when the lab key is compromised, not malicious?
- If phone-first onboarding eliminates the wallet, what new trust assumption replaces it — and is it actually better?