F Kitchen Sink

UX audit rules

Studio KS hash markers

Rule handbook metadata

Rule
DET.STUDIO.HASH · lane deterministic
Page status
current
page_version
e6c019f41fd50037fc287030f3204ebef8a0026352f1fa3a0f11cf9146539a7f
generated_at
2026-08-13T00:00:00.000Z
registry_fingerprint
aef1de6082cf0f50d463783c843dee0ffb9132fbd5ed4ea6e5bb3f031f359c72

How this rule is fixed

Not in the deterministic fixer pilot registry (stub or not yet wired). Use the After example below as the target state and remediate manually or extend pilot-registry.json.

Detection module: docs/design/ux-audit/deterministic-design-rules.md#det-studio-hash. Scroll down for Before / After examples and Evidence and remediation steps.

Purpose

Studio pages that ship KS layouts or wrappers should expose at least one data-ks-hash (and mirrored hash when static HTML) so visual catalog governance and parity checks can attribute defects to contracts.

Passing signals

  • main or shell regions include data-ks-hash with registry-backed three-letter id.
  • React primitives use ksReactPrimitiveAttrs().

Failing signals

  • Bare Vite markup with zero KS hashes on a page that claims KS reuse.

Before example

Before (failing example)

Analysis

After example

After (passing example)

Analysis

Evidence and remediation

  • page.json.ks_hash_count from capture-page.mjs.
  • Update visual-registry.yaml when adding new roots.