Certified against a hostile environment
During this arc our own build container killed five consecutive sealed runs mid-flight. The release shipped anyway, on the record: the battery runs foreground in timed slices, the assembled log feeds the same tally contract the harness has honored since R26, and DILIGENCE accepts a supplied log so a locked-down or air-gapped verifier finishes to a full verdict without one long-lived process. The failure that taught this is on the provenance page; the capability it produced is on this one.
Reliability, stated honestly
You do not have to take our word for it. Every figure on this page is computed at build or wears its label, and the harness that proves it ships with the product.
We publish no uptime percentage because we have no production history yet, and a percentage without history is theater. Here is what we publish instead, today, verifiable.
What is measured on every build
14,914 assertions across 168 suites, 0 failed; 60/60 surfaces crawled in both locales; the render boundary that turns any surface failure into a named, non-blocking card; and the latency ledger that prices decision delay instead of hiding it.
Failure modes, published first
The degradation matrix documents 10 rows of observed failure behavior from live runs, what breaks, what the operator sees, and what holds, shipped inside every release. Incumbents publish uptime after the fact; we publish failure modes up front, because a commitment you can read beforehand is the one you can check.
Availability commitments
Agreed per engagement in the MSA with recovery objectives stated in writing, monitored from week five of the certified onboarding runbook, and measured openly from the first production day. When there is history, this page will carry it with the computation shown; until then it carries the instrument.
Also from AssetShop
Fourteen other products, none of them part of EOS. Separate products, no shared runtime, tenancy or credential path. Nothing below is included in an EOS evaluation or an EOS contract. Each carries its status, and nothing is called built until it is.
- AssetShop LifeA persistent spatial world for events and communities.
- SecureLiveEncrypted live video in the browser. The shipped crossing into EOS.
- Nexus SearchSearch that returns evidence, not links.
- VideoChainVideo publishing with a chain of custody.
- VoxChainEvery kind of audio, music, voice, podcasts, audiobooks, with provenance; music publishing rights and revenue included.
- DApp NetworkHow products reach each other's capabilities.
- Marketplace & Immersive StorefrontsThe front counter for the estate.
- Recipes For IngredientsCook from what you already have.
- Open Source NewsSignal detection before it matters.
- MercurialOn-chain intelligence: regimes, tokens, DeFi, flows, with the source of every number.
- VulcanusProduct intelligence and EU packaging conformity, evidenced.
- BrainConnectConnect ideas, discover relationships.
- CortexA better place to think.
- ThresholdProperty listings with the evidence attached. A concept, not a built product.
Enter the consumer layer at assetshop.eth EOS is the Enterprise Operating System. The brand layer it belongs to is name-native. Past that line the rules are different, and it is built by Shadow Key.