Svelte 5 $state.raw Deep Proxy Isolation for High-Frequency State

--- description: Svelte 5 $state.raw Deep Proxy Isolation for High-Frequency State - Enforces immutable reference tracking via Svelte 5 '$state.raw' for high-frequency telemetry, large collections, and canvas/WebGL render buffers. Using standard deep reactive '$state' on volatile datasets creates hundreds of recursive Proxy instances per frame, triggering severe garbage collection churn and micro-task scheduler saturation. globs: src/**/*.{svelte,svelte.ts,svelte.js,ts,js} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-state-raw-deep-proxy-isolation" --- # Svelte 5 $state.raw Deep Proxy Isolation for High-Frequency State > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Wrapping high-frequency telemetry streams, large arrays, or canvas frame buffers in deeply reactive '$state' proxies. ## System Constraints You are a Principal Engineer enforcing Svelte 5 $state.raw Deep Proxy Isolation Invariant. Mandate invariants that prevent recursive proxy allocation across volatile datasets, canvas matrix states, and WebSocket telemetry streams. ## Strict Guidelines - Engineers MUST ALWAYS use '$state.raw()' when tracking datasets mutated at higher frequencies than the frame budget (>30Hz) or containing more than 1,000 discrete records. - Engineers MUST NOT initialize arrays, typed buffers, maps, or nested object trees inside standard '$state()' if those data structures are mutated in bulk during render loops or stream ingestion. - Code SHOULD trigger downstream UI updates from raw state via explicit reference reassignment ('data = [...data]' or 'data = nextValue') rather than field-level nested mutation. - Services MUST isolate internal high-throughput buffers into non-reactive or raw reactive primitives and only publish snapshot references to the view layer. - Components NEVER attach '$state()' deep proxies to WebGL buffers, Canvas 2D contexts, audio graph nodes, or high-throughput WebSocket message queues. ## Bad vs Good Implementations ### High-Frequency Telemetry Ingestion (Telemetry Buffer) #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Standard '$state' traverses and wraps every nested property in a reactive proxy. When appending telemetry at high frequencies, the runtime incurs massive allocation overhead and scheduler thrashing, leading to dropped frames. ```typescript import { $state } from 'svelte'; interface TelemetryPoint { timestamp: number; coords: [number, number, number]; metrics: Record<string, number>; } // ANTI-PATTERN: Standard $state recursively wraps every array element and nested metric object in a Proxy. // Ingestion at 60Hz creates thousands of Proxy allocations per second, degrading GC performance. export class FlightTracker { points = $state<TelemetryPoint[]>([]); pushMetric(point: TelemetryPoint) { this.points.push(point); // Triggers deep proxy traversal and microtask scheduler contention if (this.points.length > 5000) { this.points.shift(); } } } ``` #### Production Standard (Correct) > **Standard**: '$state.raw' prevents proxy wrapping of child structures. Objects remain pristine plain JavaScript objects, eliminating garbage collection pressure and avoiding reactive graph thrashing while retaining explicit change notifications on reference replacement. ```typescript import { $state } from 'svelte'; interface TelemetryPoint { timestamp: number; coords: [number, number, number]; metrics: Record<string, number>; } // PRODUCTION FIX: $state.raw maintains a flat, non-proxied reference. // Reactivity fires strictly on root reference reassignment. export class FlightTracker { points = $state.raw<readonly TelemetryPoint[]>([]); private internalBuffer: TelemetryPoint[] = []; pushMetric(point: TelemetryPoint) { this.internalBuffer.push(point); if (this.internalBuffer.length > 5000) { this.internalBuffer.shift(); } // Publish immutable snapshot reference without proxy wrapping this.points = [...this.internalBuffer]; } } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 $state.raw Deep Proxy Isolation for High-Frequency State

Svelte 5 $state.raw Deep Proxy Isolation for High-Frequency State defines an industrial-grade behavioral standard for frontend engineering. Enforces immutable reference tracking via Svelte 5 '$state.raw' for high-frequency telemetry, large collections, and canvas/WebGL render buffers. Using standard deep reactive '$state' on volatile datasets creates hundreds of recursive Proxy instances per frame, triggering severe garbage collection churn and micro-task scheduler saturation. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.

Framework Paradigm Shift & Drift MechanicsLLMs are trained on millions of open-source repositories containing outdated code, legacy idioms, and unpatched antipatterns. When coding assistants generate implementations for this stack, they default to common statistical tokens: Wrapping high-frequency telemetry streams, large arrays, or canvas frame buffers in deeply reactive '$state' proxies. Without an explicit system instruction file, developers spend hours debugging silent failures.

Failure Modes & Production Blast Radius

Hazard Analysis: What Breaks Without This Rule

The following failure modes have been cataloged from hundreds of hours of production code reviews where AI assistants produced non-compliant implementations:

Failure Mode	AI Symptom (The Anti-Pattern)	Severity	Production Impact & Remedy
AI Hallucination & Deprecation Drift	Wrapping high-frequency telemetry streams, large arrays, or canvas frame buffers in deeply reactive '$state' proxies.	Critical	Violating this industrial standard introduces regression bugs, security risks, and unexpected runtime failures in production. Enforce explicit behavioral system directives across all AI coding assistants in your repository.
Silent Architecture Inconsistency	AI assistants produce mixed paradigms across files, creating fragmented codebase conventions.	Medium	Increases cognitive load during code reviews and leads to maintenance debt across engineering teams. Pin project conventions in .cursor/rules, CLAUDE.md, and AGENTS.md so all team agents follow identical guardrails.

Architectural Directives in Detail

Step-by-Step Production Directives

Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:

Engineers MUST ALWAYS use '$state.raw()' when tracking datasets mutated at higher frequencies than the frame budget (>30Hz) or containing more than 1,000 discrete records.

Rationale:AI models frequently generate unconstrained code here because statistical language distributions lack project-specific architectural context. Mandating this directive ensures that generated code adheres to verified industrial production requirements.