Source for Operational scale gatesSource: Fail-closed operational growth gatesTable: inline gate values backed by growth/quality/gates.jsonLoads the fail-closed scale gates and their next evidence-producing action. Scale status is hold. Public outreach and acquisition scaling remain gated on provider clearance, crash diagnosis, source-synced signed phone, Wear OS, and Apple artifacts, complete physical-device coverage, and critical console guardrails.
SELECT * FROM (VALUES ('ios_crash_gate','iOS crash gate','blocked','Authenticated App Store Connect confirms one iOS 1.0.1 crash on 2026-08-25, but privacy suppression exposes no device, OS, crash report, stack, or UUID. Exact commit 97c26cb hardens reachable crash paths and passed 40 bounded simulator cold launches without a captured matching failure, but those preventive results cannot be attributed to the historical event and do not replace symbolication, physical iPhone QA, or post-rollout evidence.','Restore Organizer developer-account access or obtain the diagnostic report, then symbolicate, reproduce, fix, and re-smoke'),('open_meteo_promotion_clearance','Open-Meteo promotion clearance','pending','The authenticated Gmail thread and in:anywhere searches were checked read-only at 2026-08-29 10:22:53 +05:00. The clarification sent to info@open-meteo.com at 06:05:07 remains the thread''s only message with label SENT; no inbound Open-Meteo reply is indexed in this account. This does not prove delivery or cover another account or a future/unindexed reply. Written clearance remains absent.','Monitor the sent thread and record an unambiguous written response'),('release_artifact_source_sync','Release artifact source sync','blocked','Exact commit 97c26cb resolves to Android phone 1.1.0 (8), Wear OS 1.1.0 (1000008), and Apple 1.1.0 (6). Phone AAB SHA-256 c89b311f2227ecad6ff0f80d8f18529348f52118655b8c70112c2aef48d1c23c and mapping SHA-256 0e1624387e2829c90b690a9c288d4140545df68ecbf523d98e36d704b8150988 pass Bundletool and embedded-VCS checks but the AAB has 0 signature entries. The retained signed Wear AAB ac19a0eab1a60554db309166f135e754c97205b79c4f5182164a8b21594e7dc6 embeds historical revision 4d9492a; its non-signature payload matches fresh exact output 0a0369d132d856c27625efed1b1cb3489b97e41b7c218f33957fe281ec77485c except VCS metadata, but no exact-current signed Wear bundle exists. Apple simulator hashes are app e6a43119ff23a1ffd3fb0da600bfad9334b94f3ce7a15d244afa9744d853c539, widget 0df017e7e3f01e04acdba3b7cbb304e442318b2fad4e2ca68b1fba0a391afa94, and watch 71452e1d08c9293aaf0c3b851b7335c8053b3568f06231cba0633c4758b6b462; they are ad-hoc simulator products, not archives. Android protected lookup exits 51 and Apple private-key use remains unauthorized. There is no exact-current signed phone/Wear artifact, distribution-signed Apple archive, or signed-artifact physical matrix.','Restore private signing authorization without replacing the existing identities, then create exact-current signed phone vc8, Wear 1000008, and Apple build-6 artifacts, verify identities and hashes, and record exact physical QA'),('android_physical_smoke','Android device smoke','blocked','Exact commit 97c26cb debug APK SHA-256 5680f2bd8b7f2904cd61831c774614fb1bd147239ae37a78e858209346a180f0 passed bounded QA on the dedicated physical API 25 phone and isolated API 36 emulator. Pulled installed bytes matched; both passed onboarding, live Tashkent weather, and ten cold starts, while API 25 passed Bukhara search/share and API 36 passed true-offline fallback/recovery plus deliberate first-SQL-read failure to retry UI. There is still no upload-signed vc8 or release-certificate result, and physical tablet, widget, and Wear OS coverage remains required.','Sign and verify phone vc8, then run the exact signed artifact on phone and tablet plus widget and paired Wear OS paths'),('ios_physical_smoke','iOS physical smoke','blocked','Exact commit 97c26cb Apple 1.1.0 (6) Release simulator executable hashes are app e6a43119ff23a1ffd3fb0da600bfad9334b94f3ce7a15d244afa9744d853c539, widget 0df017e7e3f01e04acdba3b7cbb304e442318b2fad4e2ca68b1fba0a391afa94, and watch 71452e1d08c9293aaf0c3b851b7335c8053b3568f06231cba0633c4758b6b462. The app passed 40 bounded cold launches, but all three products are simulator-only with ad-hoc linker signatures, no TeamIdentifier, no archive, and no upload eligibility. GUI Archive still fails at NimboWidget CodeSign, and current iPhone, iPad, widget, and watch physical coverage remains required.','Archive and distribution-sign build 6, then run the exact artifact on iPhone and iPad plus widget and paired watch paths'),('domain_activation','Domain activation','pass','At 2026-08-29 10:40–10:41 +05:00, authenticated GitHub Pages settings showed DNS check successful and Enforce HTTPS enabled. The Let''s Encrypt certificate has CN nimbo.uz, SANs nimbo.uz/www.nimbo.uz, and validates for both hosts. WHOIS, .uz delegation, authoritative Cloudflare records, and independent 1.1.1.1/8.8.8.8 resolution pass. HTTPS returns 200 with verification result 0 for all 12 published UZ-root/RU/EN landing, press, privacy, and support routes plus growth, robots, sitemap, and the valid metadata schema. HTTP apex redirects to HTTPS; HTTP www reaches HTTPS apex in two redirects; HTTPS www redirects directly to HTTPS apex. All 12 localized HTML routes have the expected HTTPS canonical and language. Uzbek intentionally uses ' || chr(47) || ' rather than a separate ' || chr(47) || 'uz' || chr(47) || ' route.','Maintain dated DNS, certificate, redirect, canonical, and localized-route verification at each release'),('store_policy_console_clearance','Store policy console clearance','pass','The 2026-08-28 App Store read-only check found no open review/compliance action. The authenticated Google Play capture at 2026-08-29 08:41 +05:00 explicitly reported no policy issues and no unpublished changes; production remained active at 1.0.2 (6), 100%. This is point-in-time Console evidence, not a guarantee against later review. See growth/quality/store-policy-console-2026-08-28.md and growth/quality/google-play-console-2026-08-29.md.','Re-check both store policy surfaces with the next weekly UZ console evidence window')) AS gates(gate_id,gate,status,evidence,next_action)