Audience map
Each public reader gets a narrow first path. The site should not make them learn the whole chain before they can try the product.
Market translation
checking
Audience paths
checking
Safe comparison categories
Infra can be compared by product shape: storage work, provider work, proof work, public memory, retention, and reconstruction.
Comparison categories
checking
Comparison boundaries
These are the phrases the public surface should refuse until live evidence proves the exact claim.
Comparison boundaries
checking
Audience boundaries
checking
What to try first
Public value comes from the loop, not from the slogan.
Evidence rule
Infra can look similar to several categories without claiming to replace them. The receipt trail decides what can be said.
Allowed
Receipt-first storage work, public memory, proof labels, paid retrieval, and contract-bound service work.
Blocked
Production readiness, named competitor attacks, automatic provider rewards, universal durability, private payload disclosure, and unsupported economics.
Source
Public stats, source-truth recovery packet, chain status, receipt examples, endpoint contracts, and explicit stale/refusal labels.
Live proof
Live claims wait for runtime receipt, packet acknowledgement, provider settlement, terminal lifecycle, or recovery evidence.