1. Publication Contract
The deterministic publication contract builds the journal and checks canonical URLs, structured data, multilingual metadata, sitemap coverage, internal links, Market OS evidence boundaries and other release invariants before deployment.
2. Translation Parity Contract
Managed EN / RU / zh-CN publication groups must preserve sibling routes, locale identity, reciprocal hreflang, visible language switching, action surfaces and evidence-source structure. A green parity check proves structural equivalence, not perfect prose fluency.
3. Corrections + Version History Contract
Registered publications have an append-only temporal identity. Version transitions, change semantics and evidence URLs are checked so a published claim cannot be silently rewritten while still appearing to be the same recorded state.
Open Corrections & Version History →
4. RSS / Subscribe Contract
Multilingual RSS feeds are generated from published HTML rather than a separately maintained article list. Feed ordering, locale routing, RSS autodiscovery and deterministic lastBuildDate are verified before deploy, then the public feeds are fetched again after GitHub Pages succeeds.
| Feed property | Rule | Boundary |
|---|---|---|
| Identity | RSS 2.0 + stable Atom self-link | Reader applications can resolve a stable feed URL. |
| Ordering | Explicit publication dates, newest first | No wall-clock build timestamp masquerading as editorial change. |
| Locale | EN / RU / zh-CN routes stay in their own feeds | No language mixing caused by filename drift. |
| Live proof | Public feeds and representative item routes are re-fetched | Build success alone is not treated as deployment success. |
5. Experience + UI Geometry Contract
Representative pages are audited with pinned Lighthouse profiles and explicit geometry rules. Performance, accessibility, best practices, SEO, touch-target size, image behavior, overflow and layout stability are release properties rather than informal visual impressions.
| Signal | Initial budget | Why it matters |
|---|---|---|
| Performance | ≥ 80 mobile / ≥ 90 desktop | Detect meaningful lab regressions. |
| Accessibility | ≥ 95 | Protect keyboard, assistive-technology and readable interaction paths. |
| Best Practices | ≥ 95 | Catch browser/platform regressions and unsafe defaults. |
| SEO | ≥ 95 | Complement deterministic metadata checks with rendered-page checks. |
| Primary target | ≥ 44 × 44 px | Keep important controls comfortably actionable on touch screens. |
| CLS | ≤ 0.10 | Protect readers from unstable layouts. |
6. Multilingual Visual Regression
The homepage, core multilingual articles, Quality, Corrections and Measurement surfaces are captured at phone, tablet and desktop viewports. Horizontal overflow, clipped key content, watched elements outside the viewport and undersized primary controls are blocking defects. Raw pixel-diff percentage remains advisory because legitimate editorial changes also alter screenshots.
7. Live Experience Audit
After GitHub Pages reports success, the public site is measured again. This closes the gap between “the branch built correctly” and “the reader can actually reach the deployed surface.” Live evidence is retained with deploy/run context.
8. Measurement, Privacy & Collector Contract
Site Health v0.8 keeps the v0.7 browser measurement boundary and adds a selected collector architecture without activating production transport:
The browser runtime has four allowlisted events and a five-field payload. It creates no cookie, local/session storage identity or fingerprint, sends no referrer, user-agent, screen/device fields, email/name, free text or exact client timestamp, and honors Global Privacy Control and Do Not Track. Automated browser audits are suppressed so Site Health cannot manufacture its own readership.
| Measurement surface | v0.8 contract | What it does not prove |
|---|---|---|
meaningful_read | Visible ≥ 45 s and scroll depth ≥ 60% | Comprehension, agreement or demand. |
hot_question_view | Hot question ≥ 60% visible | That the reader considered or answered it. |
workflow_intake_open | Public GitHub intake link activated | That a workflow was submitted. |
verified_workflow_open | Pilot description activated from a market-question surface | Pilot qualification or willingness to pay. |
| Collector | Minimal Cloudflare Worker → Workers Analytics Engine; exact five-field allowlist | That Cloudflare transport metadata does not exist, or that aggregate events represent a person/session. |
The selected Worker does not read, hash, persist or export IP, User-Agent, referrer, cookies, geography, visitor IDs or session IDs. Production remains disabled until a deployed endpoint passes live CORS/schema and synthetic-write checks and `RESONANCE_ANALYTICS_ENDPOINT` is explicitly configured.
Evidence produced
Publication, feed, translation, history, analytics and collector rules are executable rather than implied.
Lighthouse, UI geometry and visual artifacts expose rendered regressions that static checks cannot see.
Corrections, Subscribe and Measurement pages expose important trust boundaries outside the CI interface.
Post-deploy audits re-fetch public Pages surfaces instead of assuming deployment from a successful local build.
What the numbers do not prove
A green Site Health gate is controlled evidence, not a universal quality certificate. It does not prove Google ranking, real-user Core Web Vitals, factual completeness, nuanced translation quality, visual taste, reader comprehension, workflow demand, product-market fit or revenue. Those claims require their own evidence.
Inspect the evidence
Every health claim should be traceable.
Use GitHub Actions for current contracts, the public history for managed corrections, and Measurement & Privacy for the analytics and collector boundary.