Fables opinion on valbeat

[OisinKyne]

All checks pass: type check clean, 8/8 tests, lint clean, and the full static export (all 729 share pages) builds. Net result is −19 lines. Here's what I found and changed:

The big structural fix: one vocabulary for the Stage meme

Stage naming was defined in four separate places with conflicting copy — the landing said "Exposed / Slashing-averse / Downtime-averse" while the results page, stage ladder, and OG images said "Getting started / Safety / Liveness". If you want "Stage 1, Stage 2" to spread as a meme, every surface has to say the same thing. There's now a single STAGE_META export in lib/rubric/index.ts:60 (name, kind, tagline, tone per stage), and the results hero, share card, stage ladder, landing stage cards, methodology, and OG metadata all read from it. A new test guards it.

Same treatment for slice labels: the rubric said "Provider"/"Geographic" while the landing kept its own duplicate label map saying "Provider Diversity"/"Geographic Diversity". The rubric labels are now canonical and the landing's READ_LABEL and ORDER maps are deleted — it renders straight from SLICES, in the deliberate worst-failure-first order.

Accuracy and grammar in the rub
- Client diversity why claimed e you to lose 100% of funds" —overstated. It now correctly describes mass correlated slashing when validators follow a supermajority fork.

• Key custody why: "an attacker can sign to slash your stake" → "sign slashable messages with your entire stake".
• OS diversity why: fixed "jeopardise a huge amount of validators" (grammar + British spelling) → "one poisoned updatry node — and every key — atonce". - Tips: fixed "no single entityissing space in "setup(addproviders", the tangled OS yellow tip, and reworded several to say nodes rather than validators (the active/active ptake).
• Standardized valOS branding (was "VALOS — Validator Operator Standards" on methodology, "valOS" in the header) and Amer
  Geo slice de-jurisdictioned
  Per your direction: the geo why and natural disasters, with"local policy shifts" as a trailing mention. The maxed-slice line "No single jurisdiction can stop or censor you" became n take your validator offline",and the Stage 2 lines now say "slash it or stop it" rather than leading with censorship — the Ethereum-values framing (ce survives in the longer Stage 2result copy, where it reads as values rather than threat model.
  UX and small correctness fixes
• Blockers panel: "2 wins from Stage 1" → "2 wins away from Stage 1"; legend "Yellow · partial" → "partially mitigatedons" where everything else says"slices". - Share modal note no longer prxplains the actual privacymodel: the link encodes the six colors, nothing is stored. - twitter.com/intent/tweet → x.
• Share-page canonical/og:url now includes the trailing slash the site enforces (trailingSlash: true), so it maly land on.
• Landing hero: "you always (sometimes unknowingly) pick an operator" → "you pick an operator — sometimes without kng "Two stages" phrasing (thereare three stages, two to climb); hardcoded /assess/ in methodology now uses ASSESS_PATH. - Dead code removed: unused SLInow-unused sharePreviewPath.
  Not needed: OG PNG regeneration images render are unchanged, so the 729 PNGs are still correct.
  Left alone deliberately: "operatooor" (reads as an intentional meme), the 420 ms auto-advance (feels right), andine (works correctly; a rewritewould be churn without user-visible gain). One thing to consider for a future pass: OS and CPU are binary questions but shose positions (the 3⁶ URL space) — the yellow tips for them are only reachable via hand-crafted URLs, which is harmless but worth remembering when v1.2 for