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: bun-worker-zero-copy-transfer-boundaries

Bun 1.2 Clustered Worker Zero-Copy Transfer and Ownership Boundary Standards

Enforces strict memory ownership semantics and explicit zero-copy transfer lists when passing binary payloads across Bun 1.2 worker pools. Disallows implicit structured cloning of large TypedArrays and prevents use-after-transfer race conditions on detached ArrayBuffers.

Prohibited Anti-Pattern: Implicit Structured Clone Memory Duplication and Post-Transfer Access on Detached Buffers

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Bun 1.2 Clustered Worker Zero-Copy Transfer and Ownership Boundary Standards - Enforces strict memory ownership semantics and explicit zero-copy transfer lists when passing binary payloads across Bun 1.2 worker pools. Disallows implicit structured cloning of large TypedArrays and prevents use-after-transfer race conditions on detached ArrayBuffers.
globs: src/**/*.{ts,js}, workers/**/*.{ts,js}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/bun-worker-zero-copy-transfer-boundaries"
---

# Bun 1.2 Clustered Worker Zero-Copy Transfer and Ownership Boundary Standards

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Implicit Structured Clone Memory Duplication and Post-Transfer Access on Detached Buffers

## System Constraints
You are a Principal Engineer enforcing Bun 1.2 Clustered Worker Zero-Copy Transfer Boundaries. Mandate explicit transfer lists for ArrayBuffers, prevent use-after-transfer access on detached memory, ensure thread-safe structured clone payloads, and eliminate implicit buffer serialization bottlenecks.

## Strict Guidelines
- Engineers MUST ALWAYS pass the backing ArrayBuffer in the postMessage transfer list (`[buffer]` or `[view.buffer]`) when dispatching large binary payloads across worker boundaries.
- Engineers MUST NOT access, read, or mutate an ArrayBuffer or its TypedArray views after transferring ownership to a worker thread.
- Engineers MUST verify whether a TypedArray is a sliced view before transferring; if `byteOffset !== 0` or `byteLength !== buffer.byteLength`, create an independent copy or slice before transferring to prevent leaking unassociated memory.
- Code SHOULD explicitly clear or nullify local references immediately after transferring ownership to enforce linear-type move semantics in garbage-collected environments.
- Services MUST use SharedArrayBuffer paired with Atomics solely when concurrent, bidirectional in-place mutation is provably necessary; otherwise, default to explicit zero-copy transfer ownership handover.
- Components NEVER pass Node.js Buffer instances directly into transfer lists without extracting the underlying ArrayBuffer (`buffer.buffer`).

## Bad vs Good Implementations
### Zero-Copy ArrayBuffer Transfer across Bun Worker Pools

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Failing to pass the underlying ArrayBuffer in the postMessage transfer list forces Bun's JavaScript engine to serialize and deep-copy the entire 50MB buffer via structured clone, causing significant throughput degradation and heap bloat. Retaining references encourages silent concurrent mutation bugs.
```typescript
import { Worker } from 'bun';

const worker = new Worker(new URL('./task-worker.ts', import.meta.url).href);
const largePayload = new Uint8Array(50 * 1024 * 1024); // 50MB

// ANTI-PATTERN: Omitting the transfer list causes Bun to execute a deep structured clone,
// duplicating 50MB of memory on the heap and triggering GC pressure.
worker.postMessage({
  type: 'PROCESS_FRAME',
  data: largePayload,
});

// ANTI-PATTERN: Retaining and using the buffer concurrently leads to unexpected state
console.log('Buffer still accessible:', largePayload[0]);
```

#### Production Standard (Correct)
> **Standard**: Passing `bufferToTransfer` in the second argument (`[bufferToTransfer]`) transfers memory ownership directly to the worker thread without copying (O(1) operation). The originating thread's ArrayBuffer is instantly detached (`byteLength === 0`), and local references are nullified to prevent use-after-transfer access.
```typescript
import { Worker } from 'bun';

const worker = new Worker(new URL('./task-worker.ts', import.meta.url).href);
let largePayload: Uint8Array | null = new Uint8Array(50 * 1024 * 1024); // 50MB

// Ensure payload owns the entire buffer before transferring
const bufferToTransfer: ArrayBuffer = largePayload.byteOffset === 0 &&
  largePayload.byteLength === largePayload.buffer.byteLength
    ? largePayload.buffer
    : largePayload.slice().buffer;

// Explicit zero-copy ownership transfer via the transfer list parameter
worker.postMessage(
  {
    type: 'PROCESS_FRAME',
    data: bufferToTransfer,
  },
  [bufferToTransfer]
);

// Enforce move semantics locally: buffer is now detached (byteLength === 0)
largePayload = null;

if (bufferToTransfer.byteLength !== 0) {
  throw new Error('Invariant Violation: Buffer was not detached during zero-copy transfer');
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Bun Inspector Profiler MCP
Analyzes memory allocations, thread boundaries, and detached buffer state across Bun worker pools.
Recommended Agent Skills (askills.dev)

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

Bun Worker Throughput Benchmarking
CLI automation script to verify zero-copy throughput and identify structured clone serialization overhead.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Bun 1.2 Clustered Worker Zero-Copy Transfer and Ownership Boundary Standards

Bun 1.2 Clustered Worker Zero-Copy Transfer and Ownership Boundary Standards defines an industrial-grade behavioral standard for backend engineering. Enforces strict memory ownership semantics and explicit zero-copy transfer lists when passing binary payloads across Bun 1.2 worker pools. Disallows implicit structured cloning of large TypedArrays and prevents use-after-transfer race conditions on detached ArrayBuffers. 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: Implicit Structured Clone Memory Duplication and Post-Transfer Access on Detached Buffers 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 DriftImplicit Structured Clone Memory Duplication and Post-Transfer Access on Detached BuffersCritical
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 pass the backing ArrayBuffer in the postMessage transfer list (`[buffer]` or `[view.buffer]`) when dispatching large binary payloads across worker boundaries.

Engineers MUST ALWAYS pass the backing ArrayBuffer in the postMessage transfer list (`[buffer]` or `[view.buffer]`) when dispatching large binary payloads across worker boundaries.

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 access, read, or mutate an ArrayBuffer or its TypedArray views after transferring ownership to a worker thread.

Engineers MUST NOT access, read, or mutate an ArrayBuffer or its TypedArray views after transferring ownership to a worker thread.

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

Engineers MUST verify whether a TypedArray is a sliced view before transferring

Engineers MUST verify whether a TypedArray is a sliced view before transferring; if `byteOffset !== 0` or `byteLength !== buffer.byteLength`, create an independent copy or slice before transferring to prevent leaking unassociated memory.

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

Code SHOULD explicitly clear or nullify local references immediately after transferring ownership to enforce linear-type move semantics in garbage-collected environments.

Code SHOULD explicitly clear or nullify local references immediately after transferring ownership to enforce linear-type move semantics in garbage-collected environments.

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

Services MUST use SharedArrayBuffer paired with Atomics solely when concurrent, bidirectional in-place mutation is provably necessary

Services MUST use SharedArrayBuffer paired with Atomics solely when concurrent, bidirectional in-place mutation is provably necessary; otherwise, default to explicit zero-copy transfer ownership handover.

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

Components NEVER pass Node.js Buffer instances directly into transfer lists without extracting the underlying ArrayBuffer (`buffer.buffer`).

Components NEVER pass Node.js Buffer instances directly into transfer lists without extracting the underlying ArrayBuffer (`buffer.buffer`).

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 Bun 1.2 Clustered Worker Zero-Copy Transfer and Ownership Boundary Standards critical for AI coding assistants?

Enforces strict memory ownership semantics and explicit zero-copy transfer lists when passing binary payloads across Bun 1.2 worker pools. Disallows implicit structured cloning of large TypedArrays and prevents use-after-transfer race conditions on detached ArrayBuffers. 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 (Implicit Structured Clone Memory Duplication and Post-Transfer Access on Detached Buffers) 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

Bun