AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
backendcritical PriorityID: nats-jetstream-deterministic-deduplication-window-partitioning

Deterministic Deduplication Window Partitioning in NATS JetStream 2.11

Enforces strict broker-level sequence-pinned deduplication windows across distributed edge topologies in NATS JetStream 2.11+. Eliminates edge clock-drift anomalies and split-brain replays by partitioning deduplication keys by deterministic sequence boundaries, domain partitions, and bounded epoch buckets rather than volatile wall-clock intervals.

Prohibited Anti-Pattern: Relying on Wall-Clock Timestamps and Ephemeral UUIDs for JetStream Deduplication Across Edge Topologies

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Deterministic Deduplication Window Partitioning in NATS JetStream 2.11 - Enforces strict broker-level sequence-pinned deduplication windows across distributed edge topologies in NATS JetStream 2.11+. Eliminates edge clock-drift anomalies and split-brain replays by partitioning deduplication keys by deterministic sequence boundaries, domain partitions, and bounded epoch buckets rather than volatile wall-clock intervals.
globs: src/**/*.{ts,tsx,js,mjs}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/nats-jetstream-deterministic-deduplication-window-partitioning"
---

# Deterministic Deduplication Window Partitioning in NATS JetStream 2.11

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Relying on Wall-Clock Timestamps and Ephemeral UUIDs for JetStream Deduplication Across Edge Topologies

## System Constraints
You are a Principal Software Architect enforcing deterministic deduplication guarantees in NATS JetStream 2.11+ deployments. You must prevent data loss, double-processing, and window-expiry race conditions in distributed edge-to-core topologies by mandating partitioned deduplication headers, deterministic sequence alignment, and verification of broker deduplication acknowledgments.

## Strict Guidelines
- Engineers MUST ALWAYS construct the `Nats-Msg-Id` header using deterministic partition components: `<partition-id>.<epoch-boundary>.<sha256-payload-fingerprint>` to prevent window eviction races.
- Engineers MUST NOT rely on unpartitioned UUIDs (e.g., `crypto.randomUUID()`) or raw local wall-clock timestamps (`Date.now()`) as `Nats-Msg-Id` across edge brokers subject to network partitions.
- Stream configurations MUST explicitly configure `duplicate_window` (in nanoseconds) aligned strictly with the maximum network partition recovery window and max retry interval.
- Publishers MUST inspect the `PubAck.duplicate` boolean field on every publish acknowledgment to handle broker-acknowledged deduplicated packets without treating them as unhandled exceptions.
- Code MUST set `Nats-Expected-Last-Msg-Id` or `Nats-Expected-Last-Subject-Seq` headers on publish options when linearizing state mutations per edge partition.
- Services MUST NEVER configure consumer ack policies as `AckNone` or `AckAll` when processing cross-edge partitioned streams; consumer ack policy MUST be `AckExplicit`.

## Bad vs Good Implementations
### JetStream Edge Publishing with Deterministic Deduplication Partitioning

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Using non-deterministic random UUIDs prevents JetStream from correlating retried messages if a network blip causes local reconnect cycles. When edge clocks drift or out-of-order retries occur outside standard window margins, duplicate deliveries are silently committed.
```typescript
import { connect, JSONCodec, headers } from 'nats';

interface DeviceReading {
  deviceId: string;
  reading: number;
}

export async function publishReading(nc: any, reading: DeviceReading) {
  const js = nc.jetstream();
  const jc = JSONCodec();
  const h = headers();

  // ANTI-PATTERN: Random UUID coupled with wall-clock time leads to
  // double-processing during edge reconnection if retries slip outside
  // the default 2-minute sliding duplicate_window.
  h.set('Nats-Msg-Id', `${crypto.randomUUID()}_${Date.now()}`);

  const ack = await js.publish('telemetry.readings', jc.encode(reading), { headers: h });
  return ack;
}
```

#### Production Standard (Correct)
> **Standard**: Constructs an immutable deterministic deduplication token containing the partition identity, monotonic sequence boundary, window epoch, and payload hash. Validates the `ack.duplicate` flag to ensure the consumer and edge gateway safely handle retries without state duplication.
```typescript
import { connect, JSONCodec, headers, JetStreamClient, PubAck } from 'nats';
import { createHash } from 'node:crypto';

interface DeviceReading {
  deviceId: string;
  reading: number;
  sequenceNumber: number;
}

const EPOCH_WINDOW_MS = 300_000; // 5-minute deterministic window slice

export async function publishReadingDeterministic(
  js: JetStreamClient,
  subject: string,
  reading: DeviceReading
): Promise<PubAck> {
  const jc = JSONCodec<DeviceReading>();
  const h = headers();

  // Deterministic Window Epoch: locks deduplication boundary to edge sequence chunks
  const epochBucket = Math.floor(Date.now() / EPOCH_WINDOW_MS) * EPOCH_WINDOW_MS;
  const payloadDigest = createHash('sha256')
    .update(JSON.stringify(reading))
    .digest('hex')
    .substring(0, 16);

  // Format: <partition-id>.<sequence-boundary>.<epoch-bucket>.<payload-hash>
  const deterministicMsgId = `${reading.deviceId}.${reading.sequenceNumber}.${epochBucket}.${payloadDigest}`;
  h.set('Nats-Msg-Id', deterministicMsgId);

  // Enforce broker-level sequence validation to guarantee contiguous ingest
  const ack: PubAck = await js.publish(subject, jc.encode(reading), {
    headers: h,
    timeout: 5000,
  });

  if (ack.duplicate) {
    // Invariant: duplicate acknowledgment indicates idempotent edge retry handled by NATS 2.11+
    return ack;
  }

  return ack;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

NATS JetStream Management MCP
Inspects JetStream streams, validates duplicate_window configurations, and tracks consumer sequence drifts.
Recommended Agent Skills (askills.dev)

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

NATS CLI JetStream Audit Tool
Validates stream configurations (`nats stream info`) and asserts duplicate window retention parameters.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Deterministic Deduplication Window Partitioning in NATS JetStream 2.11

Deterministic Deduplication Window Partitioning in NATS JetStream 2.11 defines an industrial-grade behavioral standard for backend engineering. Enforces strict broker-level sequence-pinned deduplication windows across distributed edge topologies in NATS JetStream 2.11+. Eliminates edge clock-drift anomalies and split-brain replays by partitioning deduplication keys by deterministic sequence boundaries, domain partitions, and bounded epoch buckets rather than volatile wall-clock intervals. 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: Relying on Wall-Clock Timestamps and Ephemeral UUIDs for JetStream Deduplication Across Edge Topologies 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 DriftRelying on Wall-Clock Timestamps and Ephemeral UUIDs for JetStream Deduplication Across Edge TopologiesCritical
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 construct the `Nats-Msg-Id` header using deterministic partition components

Engineers MUST ALWAYS construct the `Nats-Msg-Id` header using deterministic partition components: `<partition-id>.<epoch-boundary>.<sha256-payload-fingerprint>` to prevent window eviction races.

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 rely on unpartitioned UUIDs (e.g., `crypto.randomUUID()`) or raw local wall-clock timestamps (`Date.now()`) as `Nats-Msg-Id` across edge brokers subject to network partitions.

Engineers MUST NOT rely on unpartitioned UUIDs (e.g., `crypto.randomUUID()`) or raw local wall-clock timestamps (`Date.now()`) as `Nats-Msg-Id` across edge brokers subject to network partitions.

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

Stream configurations MUST explicitly configure `duplicate_window` (in nanoseconds) aligned strictly with the maximum network partition recovery window and max retry interval.

Stream configurations MUST explicitly configure `duplicate_window` (in nanoseconds) aligned strictly with the maximum network partition recovery window and max retry interval.

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

Publishers MUST inspect the `PubAck.duplicate` boolean field on every publish acknowledgment to handle broker-acknowledged deduplicated packets without treating them as unhandled exceptions.

Publishers MUST inspect the `PubAck.duplicate` boolean field on every publish acknowledgment to handle broker-acknowledged deduplicated packets without treating them as unhandled exceptions.

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

Code MUST set `Nats-Expected-Last-Msg-Id` or `Nats-Expected-Last-Subject-Seq` headers on publish options when linearizing state mutations per edge partition.

Code MUST set `Nats-Expected-Last-Msg-Id` or `Nats-Expected-Last-Subject-Seq` headers on publish options when linearizing state mutations per edge partition.

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.
6

Services MUST NEVER configure consumer ack policies as `AckNone` or `AckAll` when processing cross-edge partitioned streams

Services MUST NEVER configure consumer ack policies as `AckNone` or `AckAll` when processing cross-edge partitioned streams; consumer ack policy MUST be `AckExplicit`.

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 Deterministic Deduplication Window Partitioning in NATS JetStream 2.11 critical for AI coding assistants?

Enforces strict broker-level sequence-pinned deduplication windows across distributed edge topologies in NATS JetStream 2.11+. Eliminates edge clock-drift anomalies and split-brain replays by partitioning deduplication keys by deterministic sequence boundaries, domain partitions, and bounded epoch buckets rather than volatile wall-clock intervals. 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 (Relying on Wall-Clock Timestamps and Ephemeral UUIDs for JetStream Deduplication Across Edge Topologies) 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 BACKEND Rules

View all rules →
backend
42

Fastify 5 Schema Compilers & Encapsulation Production Standard

Fastify relies on lexical encapsulation contexts to sandbox decorators, hooks, and compiled validation/serialization schemas without memory leaks or cross-tenant bleed. In Fastify 5, misuse of global compilers or failing to encapsulate plugin boundaries causes compiled `fast-json-stringify` serializers and Ajv validators to either crash on duplicate IDs, leak private data across sibling scopes, or bypass JIT compilation optimizations. Production services must enforce strict encapsulation hierarchies and type-safe schema compilation across every routing subtree.

backend
68

Bun Embedded SQLite WAL Mode & Transaction Synchronization Standard

Production database standard for bun:sqlite. Mandates enabling Write-Ahead Logging (PRAGMA journal_mode = WAL), busy timeouts, and using db.transaction() for atomic operations without lock starvation.

backend
68

Drizzle ORM Batch API & Interactive Transaction Isolation Standard

Production database standard for Drizzle ORM (PostgreSQL & MySQL). Mandates using db.batch() over HTTP drivers to prevent round-trip waterfalls, explicit db.transaction() with serializable/read-committed isolation, and strictly avoids unawaited query promises.

1 Rule in Stack

Deterministic