Svelte 5 Runes Reactive Effect Cycle Termination and State Graph Invariant

--- description: Svelte 5 Runes Reactive Effect Cycle Termination and State Graph Invariant - Enforces deterministic termination on Svelte 5 `$effect` executions by strictly isolating signal reads from reactive mutations. Prevents recursive scheduler microtask loops and main-thread exhaustion across cross-component signal boundaries. globs: src/**/*.{svelte,svelte.ts,svelte.js,ts} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/svelte-5-runes-effect-cycle-termination-invariant" --- # Svelte 5 Runes Reactive Effect Cycle Termination and State Graph Invariant > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Bi-Directional State Synchronization and Self-Triggering Signal Mutations in $effect Blocks ## System Constraints You are a Principal Software Architect enforcing the Svelte 5 Runes Reactive Effect Cycle Termination Invariant. You must reject any code where `$effect` or `$effect.pre` blocks mutate `$state` dependencies that are tracked within the same execution path without an explicit cycle fence (`untrack`). Enforce unidirectional data flow, prioritize `$derived` over synchronization effects, and ensure shared `.svelte.ts` signal graphs never trigger recursive microtask flushes. ## Strict Guidelines - Engineers MUST ALWAYS wrap non-triggering dependency reads with `untrack(() => ...)` when reading and writing related state within an `$effect`. - Engineers MUST NOT mutate any `$state` or `$bindable` prop inside an `$effect` if that state can be derived declaratively via `$derived` or `$derived.by`. - Code SHOULD replace multi-component state synchronization effects with explicit, event-driven mutator methods hosted in shared `.svelte.ts` modules. - Services MUST implement explicit guard conditions and depth checks if external event streams trigger state changes from within effect boundaries. - Components NEVER establish circular `$effect` ping-pong bindings where Child updates Parent `$state` in response to Parent updating Child `$state`. ## Bad vs Good Implementations ### Preventing Infinite Microtask Feedback Loop in Cross-Component Filter Synchronization #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Both $effect blocks create a bi-directional dependency cycle between local `$bindable` prop state and the global rune store. A change in one triggers the other synchronously across microtask flushes, locking the main thread and crashing with 'Maximum update depth exceeded'. ```typescript import { dashboardState } from './dashboardState.svelte'; let { filter = $bindable() } = $props(); // ANTI-PATTERN: Both reads and writes are tracked, causing recursive effect cycles $effect(() => { if (filter !== dashboardState.currentFilter) { dashboardState.currentFilter = filter; } }); $effect(() => { if (dashboardState.currentFilter !== filter) { filter = dashboardState.currentFilter; } }); ``` #### Production Standard (Correct) > **Standard**: The dependency graph cycle is terminated by wrapping the internal state mutation inside `untrack(...)`. Upstream changes cleanly flow downward without registering `filter` as an active subscription in the synchronization effect, while user actions update both targets imperatively. ```typescript import { untrack } from 'svelte'; import { dashboardState } from './dashboardState.svelte'; let { filter = $bindable() } = $props(); // PRODUCTION FIX: Unidirectional propagation using untrack to break dependency graph edge $effect(() => { const upstreamFilter = dashboardState.currentFilter; untrack(() => { if (filter !== upstreamFilter) { filter = upstreamFilter; } }); }); function handleUserFilterChange(newFilter: string) { filter = newFilter; dashboardState.setFilter(newFilter); } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Svelte 5 Runes Reactive Effect Cycle Termination and State Graph Invariant

Svelte 5 Runes Reactive Effect Cycle Termination and State Graph Invariant defines an industrial-grade behavioral standard for frontend engineering. Enforces deterministic termination on Svelte 5 `$effect` executions by strictly isolating signal reads from reactive mutations. Prevents recursive scheduler microtask loops and main-thread exhaustion across cross-component signal boundaries. 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: Bi-Directional State Synchronization and Self-Triggering Signal Mutations in $effect Blocks 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	Bi-Directional State Synchronization and Self-Triggering Signal Mutations in $effect Blocks	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 wrap non-triggering dependency reads with `untrack(() => ...)` when reading and writing related state within an `$effect`.

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.