Replace ANTI_DRIFT.md with frontend-specific drift prevention rules - cool idea creep, subtraction first, control plane mental model

ANTI_DRIFT.md

@@ -1,76 +1,45 @@
-# Anti-Drift Guardrail – zlh-grind
+# Anti-Drift Rules – ZLH Frontend
 
-This document exists to **actively prevent drift** during GPT-driven execution work.
+ZeroLagHub has historically suffered from "cool idea creep."
+This document exists to stop that from happening again.
 
-It is intentionally short, blunt, and enforceable.
+## Known Drift Patterns
+- Adding visual effects to compensate for unfinished features
+- Layering multiple aesthetic ideas (HUD + glow + 3D)
+- Treating the UI as a showcase instead of a tool
+- Reintroducing browser-only logic into shared utilities
 
----
+## Drift Prevention Rules
 
-## Purpose
+### 1. Subtraction First
+If something feels off:
+- Remove an effect
+- Simplify a color
+- Flatten a component
 
-- Ensure execution work does not silently become architecture work
+Never add effects to "balance" other effects.
-- Prevent re-litigation of settled decisions
-- Keep GPT sessions aligned across days and chats
-- Maintain a clean separation between *doing* and *deciding*
 
----
+### 2. One Idea Per Layer
+At most:
+- One accent color family
+- One subtle animation
+- One background texture
 
-## Canonical Authority
+If more than one exists, drift has begun.
 
-**This repository is NOT canonical.**
+### 3. Control Plane Mental Model
+Ask before merging:
+> "Would this feel appropriate in a production admin console at 2AM?"
 
-All source-of-truth documents live in:
+If no, remove it.
-- `jester/knowledge-base`
 
-If something is unclear:
+### 4. Marketing ≠ Dashboard
-- Stop
+- Marketing pages may be expressive.
-- Reference canonical docs
+- Dashboard and terminals must be calm and utilitarian.
-- Defer to Claude if architectural judgment is required
+- Product UI must never feel like a demo reel.
 
----
+## Drift Response
-
+If drift is detected:
-## Hard Stop Conditions
+1. Revert the change
-
+2. Document why it was tempting
-If any of the following occur, execution must stop:
+3. Re-apply only what serves usability
-
-- A change affects system boundaries
-- A change alters ownership between API / Agent / Frontend
-- A change modifies provisioning, DNS, or orchestration authority
-- A change contradicts the Cross-Project Tracker
-- A change feels like "we should rethink this"
-
-**Execution does not rethink architecture.**
-
----
-
-## Allowed Changes
-
-GPT execution work may:
-
-- Implement already-decided designs
-- Refactor for clarity without changing behavior
-- Add logging, validation, or safety checks
-- Document *what happened* during execution
-
----
-
-## Session Discipline
-
-At the start of every session:
-1. Read `CONSTRAINTS.md`
-2. Read this file (`ANTI_DRIFT.md`)
-3. Read the latest entry in `SESSION_LOG.md`
-
-At the end of every session:
-- Append to `SESSION_LOG.md`
-- Update `OPEN_THREADS.md` if anything is unfinished
-
----
-
-## Mental Model
-
-- **Claude decides**
-- **GPT executes**
-- **This repo records execution**
-
-Anything else is drift.