React 19 Taint API & Server Component Memory Isolation Standard

--- description: React 19 Taint API & Server Component Memory Isolation Standard - Enforces strict boundaries around cryptographic secrets, raw database entity models, and sensitive environment variables to prevent accidental serialization into React Server Component (RSC) Flight payload streams. Mandates the use of experimental_taintObjectReference and experimental_taintUniqueValue alongside Data Transfer Object (DTO) projection patterns at all boundary seams. globs: src/**/*.{ts,tsx}, app/**/*.{ts,tsx}, lib/**/*.{ts,tsx} alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/react-19-taint-api-memory-isolation-standard" --- # React 19 Taint API & Server Component Memory Isolation Standard > **Severity**: CRITICAL | **Category**: frontend > **Anti-Pattern Warning**: Leaking Raw Database Records or Cryptographic Secrets into Client Component Props and RSC Flight Streams ## System Constraints You are a Principal Engineer enforcing the React 19 Taint API & Server Component Memory Isolation Standard. You must ensure that no raw database entity instances, cryptographic tokens, or server-only environmental keys are ever passed across the Server-to-Client component boundary. Require explicit invocation of experimental_taintObjectReference for data models containing sensitive attributes and experimental_taintUniqueValue for high-entropy secrets. Enforce strict projection into pure Client-Safe DTOs (Data Transfer Objects) before passing props to 'use client' components or exposing them to RSC serialization streams. ## Strict Guidelines - Engineers MUST ALWAYS invoke 'experimental_taintObjectReference' on raw database records, ORM entities, and user session records immediately upon retrieval in server-only modules. - Engineers MUST ALWAYS invoke 'experimental_taintUniqueValue' for sensitive string primitives such as API secrets, private encryption keys, session tokens, and password hashes. - Engineers MUST NOT pass full data-layer objects or un-projected ORM models directly to Client Components ('use client') or return them from Server Actions. - Code SHOULD enforce strict TypeScript DTO contracts (e.g., using pick or zod schemas) to create whitelist-only payload shapes before passing data across the RSC boundary. - Services MUST declare 'import "server-only"' at the entry point of any module handling tainted data, cryptographic utilities, or database connections. - Components NEVER accept raw domain entities as props unless marked purely as Server Components without client boundary transitions. ## Bad vs Good Implementations ### Tainting Raw Entities and Projecting Safe DTOs for Client Serialization #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Passing the raw ORM entity directly to a Client Component embeds the entire object graph, including password hashes and 2FA secrets, into the public HTML Flight response payload stream. ```typescript import 'server-only'; import { db } from '@/lib/db'; import { UserProfileClient } from '@/components/UserProfileClient'; export async function UserPage({ userId }: { userId: string }) { const user = await db.user.findUnique({ where: { id: userId } }); if (!user) throw new Error('Not found'); // CRITICAL SECURITY RISK: Raw database entity containing hashedPassword, // internal audit logs, and twoFactorSecret passed directly to Client Component. // This leaks directly into the RSC Flight JSON stream rendered to the browser. return <UserProfileClient user={user} />; } ``` #### Production Standard (Correct) > **Standard**: Uses React 19's experimental_taintObjectReference and experimental_taintUniqueValue to trigger build/runtime exceptions if the raw object or secret is serialized. Explicitly projects to a SafeUserDTO containing only client-safe fields. ```typescript import 'server-only'; import { experimental_taintObjectReference, experimental_taintUniqueValue } from 'react'; import { db } from '@/lib/db'; import { UserProfileClient } from '@/components/UserProfileClient'; interface SafeUserDTO { id: string; name: string; avatarUrl: string | null; } export async function UserPage({ userId }: { userId: string }) { const user = await db.user.findUnique({ where: { id: userId } }); if (!user) throw new Error('Not found'); // Prevent entire raw entity from being serialized into the Flight stream experimental_taintObjectReference( 'Do not pass raw User records directly to Client Components. Project to SafeUserDTO.', user ); if (user.twoFactorSecret) { // Taint raw secret value so it cannot even be accidentally forwarded as a string experimental_taintUniqueValue( 'Sensitive 2FA secret cannot be exposed to the client.', user, user.twoFactorSecret ); } // Explicit whitelist projection to safe DTO const safeDto: SafeUserDTO = { id: user.id, name: user.name, avatarUrl: user.avatarUrl, }; return <UserProfileClient user={safeDto} />; } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Taint API & Server Component Memory Isolation Standard

React 19 Taint API & Server Component Memory Isolation Standard defines an industrial-grade behavioral standard for frontend engineering. Enforces strict boundaries around cryptographic secrets, raw database entity models, and sensitive environment variables to prevent accidental serialization into React Server Component (RSC) Flight payload streams. Mandates the use of experimental_taintObjectReference and experimental_taintUniqueValue alongside Data Transfer Object (DTO) projection patterns at all boundary seams. 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: Leaking Raw Database Records or Cryptographic Secrets into Client Component Props and RSC Flight Streams 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	Leaking Raw Database Records or Cryptographic Secrets into Client Component Props and RSC Flight Streams	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 invoke 'experimental_taintObjectReference' on raw database records, ORM entities, and user session records immediately upon retrieval in server-only modules.

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.