AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
frontendcritical PriorityID: react19-server-cache-life-dynamic-tag-invalidation

React 19 Server Cache-Life & Multi-Tenant Dynamic Tag Invalidation Invariant

Mandates cryptographically isolated, tenant-scoped dynamic cache tags and bounded cache-life profiles across React 19 Server Component caching boundaries. Eliminates multi-region edge cache desynchronization and prevents multi-tenant data bleed in distributed server environments.

Prohibited Anti-Pattern: Unscoped Global Edge Caching and State Bleed via Ambient Server Component Cache Tags

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: React 19 Server Cache-Life & Multi-Tenant Dynamic Tag Invalidation Invariant - Mandates cryptographically isolated, tenant-scoped dynamic cache tags and bounded cache-life profiles across React 19 Server Component caching boundaries. Eliminates multi-region edge cache desynchronization and prevents multi-tenant data bleed in distributed server environments.
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/react19-server-cache-life-dynamic-tag-invalidation"
---

# React 19 Server Cache-Life & Multi-Tenant Dynamic Tag Invalidation Invariant

> **Severity**: CRITICAL | **Category**: frontend
> **Anti-Pattern Warning**: Unscoped Global Edge Caching and State Bleed via Ambient Server Component Cache Tags

## System Constraints
You are a Principal Software Architect enforcing React 19 Server Cache-Life Dynamic Tag Invalidation Invariants. Your objective is to prevent edge-cache desynchronization, cache poisoning, and catastrophic multi-tenant data leaks. You must enforce explicit tenant-bound dynamic tags, strictly typed cacheLife profiles, and deterministic revalidation semantics across all Server Component and Server Action boundaries.

## Strict Guidelines
- Engineers MUST ALWAYS qualify dynamic cache tags with immutable tenant/workspace identifiers (e.g., `tenant:${tenantId}:entity:${entityId}`) within 'use cache' directives.
- Engineers MUST NOT cache tenant-private server operations using global, static, or ambient string literals without dynamic contextual tags.
- Code MUST explicitly declare `cacheLife` durations (e.g., 'seconds', 'minutes', 'hours') inside any function marked with 'use cache' to avoid indefinite or vendor-default edge retention.
- Services MUST invoke `revalidateTag` with identical multi-part tenant-prefixed tag signatures upon any write or mutation path within Server Actions.
- Components NEVER accept unscoped or ambient user session tokens across a 'use cache' boundary without factoring the session identifier into the cache parameters or dynamic cache tags.

## Bad vs Good Implementations
### Multi-Tenant Dynamic Cache-Life Invalidation Pattern

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: The dynamic cache tag uses ambient string literals without tenant prefixing, resulting in cross-tenant cache collisions at edge nodes. Furthermore, the omitted cacheLife defaults to indefinite or platform-arbitrary durations, and invalidation in the server action fails to match the original cache tag shape.
```typescript
import { unstable_cacheLife as cacheLife, unstable_cacheTag as cacheTag } from 'next/cache';

// CRITICAL FLAW: Global tag without tenant isolation; allows Tenant B to see Tenant A data
// and lacks explicit cacheLife tier, risking indefinite multi-region edge retention.
export async function getCustomerInvoices(tenantId: string, invoiceId: string) {
  'use cache';
  cacheTag('invoices', invoiceId);

  const response = await fetch(`https://api.internal/invoices/${invoiceId}`, {
    headers: { 'X-Tenant-Id': tenantId },
  });
  return response.json();
}

export async function updateInvoice(tenantId: string, invoiceId: string, data: any) {
  'use server';
  await fetch(`https://api.internal/invoices/${invoiceId}`, { method: 'POST', body: JSON.stringify(data) });
  // Flawed invalidation: does not match global tag structure deterministically
  revalidateTag(invoiceId);
}
```

#### Production Standard (Correct)
> **Standard**: Dynamic tags are strictly isolated with tenant prefixes via deterministic helper functions. Explicit cacheLife ('hours') bounds edge freshness, and Server Actions invalidate both specific entity and collection tags using the exact same multi-region key topology.
```typescript
import { unstable_cacheLife as cacheLife, unstable_cacheTag as cacheTag, revalidateTag } from 'next/cache';

type CacheProfile = 'seconds' | 'minutes' | 'hours' | 'days' | 'max';

interface InvoiceResponse {
  id: string;
  tenantId: string;
  amount: number;
  status: 'draft' | 'paid' | 'void';
}

function getInvoiceCacheTag(tenantId: string, invoiceId: string): string {
  return `tenant:${tenantId}:invoice:${invoiceId}`;
}

function getTenantInvoiceCollectionTag(tenantId: string): string {
  return `tenant:${tenantId}:invoices`;
}

export async function getCustomerInvoices(tenantId: string, invoiceId: string): Promise<InvoiceResponse> {
  'use cache';
  cacheLife('hours');
  cacheTag(getTenantInvoiceCollectionTag(tenantId), getInvoiceCacheTag(tenantId, invoiceId));

  const response = await fetch(`https://api.internal/invoices/${invoiceId}`, {
    headers: { 'X-Tenant-Id': tenantId },
  });

  if (!response.ok) {
    throw new Error(`Failed to fetch invoice ${invoiceId} for tenant ${tenantId}`);
  }

  return response.json();
}

export async function updateInvoice(
  tenantId: string,
  invoiceId: string,
  data: Partial<InvoiceResponse>
): Promise<void> {
  'use server';
  
  const response = await fetch(`https://api.internal/invoices/${invoiceId}`, {
    method: 'PATCH',
    headers: { 
      'Content-Type': 'application/json',
      'X-Tenant-Id': tenantId 
    },
    body: JSON.stringify(data),
  });

  if (!response.ok) {
    throw new Error(`Mutation failed for invoice ${invoiceId}`);
  }

  // Deterministic edge cache eviction scoped exclusively to the mutated tenant resource
  revalidateTag(getInvoiceCacheTag(tenantId, invoiceId));
  revalidateTag(getTenantInvoiceCollectionTag(tenantId));
}
```
Recommended MCP Servers (mcp-serverlist.com)

Equip agent with system tools to verify code for this stack.

Fetch Cache & Network Inspector MCP
Inspects distributed edge responses, dynamic cache headers, and validates tag propagation across edge nodes.
Recommended Agent Skills (askills.dev)

Ready-to-use executable skill functions tailored to this stack.

React 19 Next Cache Invariant CLI
Static AST verification tool ensuring all 'use cache' directives declare explicit cacheLife and tenant-scoped cacheTag calls.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: React 19 Server Cache-Life & Multi-Tenant Dynamic Tag Invalidation Invariant

React 19 Server Cache-Life & Multi-Tenant Dynamic Tag Invalidation Invariant defines an industrial-grade behavioral standard for frontend engineering. Mandates cryptographically isolated, tenant-scoped dynamic cache tags and bounded cache-life profiles across React 19 Server Component caching boundaries. Eliminates multi-region edge cache desynchronization and prevents multi-tenant data bleed in distributed server environments. 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: Unscoped Global Edge Caching and State Bleed via Ambient Server Component Cache Tags 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 ModeAI Symptom (The Anti-Pattern)SeverityProduction Impact & Remedy
AI Hallucination & Deprecation DriftUnscoped Global Edge Caching and State Bleed via Ambient Server Component Cache TagsCritical
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 InconsistencyAI 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:

1

Engineers MUST ALWAYS qualify dynamic cache tags with immutable tenant/workspace identifiers (e.g., `tenant

Engineers MUST ALWAYS qualify dynamic cache tags with immutable tenant/workspace identifiers (e.g., `tenant:${tenantId}:entity:${entityId}`) within 'use cache' directives.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
2

Engineers MUST NOT cache tenant-private server operations using global, static, or ambient string literals without dynamic contextual tags.

Engineers MUST NOT cache tenant-private server operations using global, static, or ambient string literals without dynamic contextual tags.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
3

Code MUST explicitly declare `cacheLife` durations (e.g., 'seconds', 'minutes', 'hours') inside any function marked with 'use cache' to avoid indefinite or vendor-default edge retention.

Code MUST explicitly declare `cacheLife` durations (e.g., 'seconds', 'minutes', 'hours') inside any function marked with 'use cache' to avoid indefinite or vendor-default edge retention.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
4

Services MUST invoke `revalidateTag` with identical multi-part tenant-prefixed tag signatures upon any write or mutation path within Server Actions.

Services MUST invoke `revalidateTag` with identical multi-part tenant-prefixed tag signatures upon any write or mutation path within Server Actions.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
5

Components NEVER accept unscoped or ambient user session tokens across a 'use cache' boundary without factoring the session identifier into the cache parameters or dynamic cache tags.

Components NEVER accept unscoped or ambient user session tokens across a 'use cache' boundary without factoring the session identifier into the cache parameters or dynamic cache tags.

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.
Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.
Technical Questions & Answers

Frequently Asked Technical Questions

Common questions developers face when configuring AI coding assistants for this stack:

Q:Why is React 19 Server Cache-Life & Multi-Tenant Dynamic Tag Invalidation Invariant critical for AI coding assistants?

Mandates cryptographically isolated, tenant-scoped dynamic cache tags and bounded cache-life profiles across React 19 Server Component caching boundaries. Eliminates multi-region edge cache desynchronization and prevents multi-tenant data bleed in distributed server environments. Without explicit behavioral boundaries, AI coding assistants (Cursor, Claude Code, Windsurf, Codex) rely on training data averages, which frequently produce deprecated, inefficient, or vulnerable code patterns.

Q:How does adopting this rule prevent AI hallucinations?

This rule explicitly declares what the AI must avoid (Unscoped Global Edge Caching and State Bleed via Ambient Server Component Cache Tags) and prescribes verified positive examples. Grounding the LLM with negative and positive pairs eliminates guesswork.

Q:Which AI coding environments are supported?

This specification is multi-platform compatible: Cursor (.cursor/rules/*.mdc & .cursorrules), Anthropic Claude Code (CLAUDE.md), Windsurf (.windsurfrules), Codex / Cline (AGENTS.md), and GitHub Copilot (.github/copilot-instructions.md).

Q:Can I combine this rule with other technology stacks?

Yes. Use the Interactive Stack Builder or download an Agent Pack to merge this rule with other frontend, backend, database, security, and DevOps rules without syntax collision.

Open Specification · CC BY 4.0·Free for Personal, Team & Commercial In-Repo Use

Citation & Open Source Attribution Guidelines

This specification is licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). You are completely free to adapt and share this rule in your workspace. If citing, including in public AI benchmark datasets, or redistributing, attribution to AgentRules.org is required.

Related FRONTEND Rules

View all rules →
frontend
119

SolidStart 1.0 Server Functions & Async Boundaries Production Standard

SolidStart 1.0 relies on the Vinxi bundler to split `server$` closures into independent HTTP POST RPC endpoints. Direct lexical closure over client signals within `server$` scopes or failure to demarcate async boundaries with `<Suspense>` causes silent serialization failures, client-bundle secret leaks, and SSR hydration mismatches. Enforcing strict parameter passing, runtime input validation, and Solid async primitives maintains security and fine-grained reactivity across network boundaries.

frontend
119

Astro 5 Actions & Content Layer Production Standard

Enforces strict type safety and architectural correctness for Astro 5 Server Actions and the zero-waterfall Content Layer API. Prevents runtime contract mismatches, hydration mismatches, and unhandled mutation exceptions across dynamic and prerendered boundaries. Failure to follow these patterns leads to silent data fetching waterfalls, build-time cache corruptions, and unhandled server action exceptions.

frontend
51

Nuxt 4 Nitro Server Engine & Shared Directory Production Standard

Nuxt 4 enforces strict boundary segregation between client UI in the app/ directory, backend endpoints in server/, and universal contracts in shared/. Violating cross-boundary isolation or maintaining module-scoped state in Nitro server handlers causes catastrophic cross-request data corruption and hydration mismatches under concurrent production traffic. Architects must enforce request-isolated H3 event contexts, universal serialization schemas, and strict path-alias boundaries.

1 Rule in Stack

React