Trust surface
The correctness of our numbers is not a claim; it is the output of a verifiable chain, a signed certificate, and a public incident record. This page opens that evidence to anyone.
Live-verify event integrity for the demo dataset (v2026.07.13). Each row carries the previous row's hash; if the chain breaks, the panel returns FAIL.
Snapshot generated: —
Every landing release closes with a Release Certificate JSON of the shape below. The example is the actual shape of a landing close that carried the LP4-001 exception.
{
"schema_version": "release-certificate/v1",
"sprint": "landing-refresh/LP4",
"code_sha": "f056a9a3",
"prod_deploy_date": "2026-07-06",
"urls": {
"tr": "https://ai.cosmosboard.com/",
"en": "https://ai.cosmosboard.com/en"
},
"status": "CLOSED_WITH_RELEASE_EXCEPTION",
"verdict": "SHIP",
"release_gate": {
"prod_pods_new_image": {
"status": "PASS",
"detail": "2/2 f056a9a3"
},
"rollback_ready": {
"status": "PASS",
"detail": "e34b2437 retained"
},
"route_root_200": {
"status": "PASS"
},
"route_en_200": {
"status": "PASS"
},
"regression_5_routes_200": {
"status": "PASS",
"detail": "/ /en /dashboard /login /contact"
},
"canonical_correct": {
"status": "PASS"
},
"hreflang_reciprocity": {
"status": "PASS",
"detail": "tr / en / x-default"
},
"sitemap_xml": {
"status": "PASS",
"detail": "both loc entries"
},
"robots_txt": {
"status": "PASS",
"detail": "allow / /en, disallow authed"
},
"html_lang_per_route": {
"status": "PASS",
"detail": "tr on /, en on /en"
},
"lighthouse_desktop": {
"status": "PASS",
"median": "100/100"
},
"lighthouse_a11y": {
"status": "PASS",
"median": "97/97"
},
"lighthouse_bp_seo": {
"status": "PASS",
"median": "100/100"
},
"lighthouse_mobile_perf": {
"status": "EXCEPTION",
"exception_id": "LP4-001",
"observed_median": {
"/": 85,
"/en": 88
},
"target_min": 89
},
"console_hydration": {
"status": "PASS",
"detail": "no errors surfaced during headless capture"
}
},
"exceptions": [
{
"id": "LP4-001",
"recorded_at": "2026-07-06",
"approved_by": "Platform Owner",
"metric": "Mobile Lighthouse Performance (median of 3 runs)",
"target_min": 89,
"observed": {
"pre_deploy": {
"/": {
"median": 87,
"runs": [
95,
87,
85
]
},
"/en": {
"median": 86,
"runs": [
85,
86,
86
]
}
},
"post_deploy": {
"/": {
"median": 85,
"runs": [
83,
85,
88
]
},
"/en": {
"median": 88,
"runs": [
88,
89,
88
]
}
}
},
"root_cause": "Hero + DashboardPreview render cost (frozen under LP1/LP2 Section Isolation)",
"decision": "accepted_by_platform_owner",
"scope": "one_time_v1_release_only",
"charter_change": false,
"follow_up_milestone": "landing-perf-tuning"
}
],
"signed_off_by": [
{
"role": "platform_owner",
"at": "2026-07-06"
},
{
"role": "engineering",
"at": "2026-07-06"
}
],
"evidence_bundle_ref": "change-safety/evidence/landing-refresh/LP4/"
}We keep a library where past incidents are not quietly deleted. This is the first entry: a silent domain language drift.
Every release passes through four layers. If any layer FAILs, the release stops.
Demo tenant operational isolation currently relies on provisioning constraints, not platform-wide enforcement. Full enforcement is tracked under the Demo Tenant Isolation Hardening milestone.