Container verification attempts recorded, and how many passed
- As of2026-10-19
184 / 335
runs
- Stage
- deploy_verification_runs
- Method
- one row per (slug, ran_at, lane) from the weekly verifier
- Sample
- 335
- As of
- 2026-10-19
- Note
- A failing run names the rung it failed on; the queue retries failures after 28 days (--retry-failed-after). A credentials rung means the spec needs a secret the harness does not hold, not that the install is broken.
How this was measured
- Method
- One row per (slug, ran_at, lane) from the weekly verifier.
- Window
- One reading, frozen at the report's as-of date (2026-10-19).
- Data date
- MCP call
onchain_agent_explain_number({"slug":"container-verification-attempts-recorded-and-how-many-passed"})on https://satohub.ai/api/mcp- URL
- none — A frozen report figure has no live export; the SQL below recounts it against Sato Hub's tables.
- Recount
select count(*) filter (where ok), count(*) from deploy_verification_runs;
A number from Sato Hub's own tables and public sources. It is never summed across venues, chains or stages; a sample under 20 is shown but is not a finding; “unknown” means the measurement could not be taken, never zero. Data CC-BY-4.0 — attribution: data by satohub.ai.
Reference
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Sato Hub — Container verification attempts recorded, and how many passed." Sato Hub, updated 2026-10-19, accessed 2026-10-23. https://satohub.ai/numbers/container-verification-attempts-recorded-and-how-many-passedData last refreshed 2026-10-19; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.