MEMORY
memory/localmode-1060dea9-0dc3-42b4-958d-2a6f7a6c0c58/parked-ui-consistency-audit.md
sha256 a655eed304b2fa3d · 2497 bytes ·
original held in the private archive
---
name: parked-ui-consistency-audit
description: "CLOSED as a homogenization mandate — overruled by the owner's 'UNIQUE ON PURPOSE' ruling. Only a narrow non-conflicting scope (density, contrast, tap targets) may ever be revived."
metadata:
node_type: memory
type: project
originSessionId: 0b7c5f41-bb34-4ab4-93be-fdb363f5eb40
---
# ⛔ OVERRULED — DO NOT RUN THIS AS WRITTEN
This was parked (2026-06-28) as a cross-panel structural/style consistency audit whose deliverable included **gate guards that would FAIL THE BUILD when a panel deviated from a shared pattern**. That enforcement half is **DEAD**, and the file is kept only so nobody re-derives it.
**Why it is dead:** it directly contradicts the owner's own standing ruling, recorded in [[parked-nv-overhaul-design-audit]] — the varied per-instrument gestures are *"UNIQUE ON PURPOSE"* and *"Do NOT homogenize them."* That ruling flows from the custom-1-of-1-per-screen philosophy in [[design-overhaul-direction]]. Mechanically enforcing one shared pattern across every panel is precisely the homogenization he forbade. **Running this audit as originally written would violate a direct owner instruction.** Future audits must also not re-flag per-instrument variation as a flaw.
*Correction 2026-07-20: this file previously asserted a single "established pattern" as the target standard and specified build-failing consistency guards. That premise was removed — it was in live conflict with the owner's ruling.*
## What MAY still be worth doing (narrow, non-conflicting)
Consistency dimensions that are about **legibility and reachability**, not about making screens look or behave alike:
- **Density / spacing** — comfortable and predictable, without flattening a screen's identity.
- **Contrast** — no surface below the a11y floor.
- **Tap-target size** — every control actually hittable (overlaps with [[parked-accessibility-audit]] and [[parked-mobile-audit]]).
These are safe because none of them require two panels to share a structure or an interaction gesture. Anything beyond these three needs the owner's explicit go, and must be checked against the ruling above first.
## The one durable observation worth keeping
The owner's original motivation was that **he kept requesting one-off UI fixes**, and read that as a symptom rather than a series of unrelated bugs. That instinct still stands — but the remedy is *shared foundations* (density, contrast, targets), **not** a uniform panel template.
STAMP · generated for RELEASE v2.8.5 commit 06e5180 (06e51801b38a) · archive input-tree hash c07fbfbdd2e1ddeb · 754 files · no wall-clock timestamp (regenerates identically when nothing changed).