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-guardrail

Bun 1.2 Clustered Worker Zero-Copy ArrayBuffer Transfer Guardrail

Enforces explicit ownership transfer semantics and detachment verification for ArrayBuffer payloads sent across Bun worker threads. Eliminates multi-gigabyte structured clone serialization overhead and prevents invalid memory reads on detached ArrayBuffers under extreme messaging throughput.

Prohibited Anti-Pattern: Implicit structured cloning of binary payloads and post-transfer access to detached ArrayBuffers

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Bun 1.2 Clustered Worker Zero-Copy ArrayBuffer Transfer Guardrail - Enforces explicit ownership transfer semantics and detachment verification for ArrayBuffer payloads sent across Bun worker threads. Eliminates multi-gigabyte structured clone serialization overhead and prevents invalid memory reads on detached ArrayBuffers under extreme messaging throughput.
globs: src/**/*.{ts,js}, workers/**/*.{ts,js}, lib/**/*.{ts,js}
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/bun-worker-zero-copy-transfer-guardrail"
---

# Bun 1.2 Clustered Worker Zero-Copy ArrayBuffer Transfer Guardrail

> **Severity**: CRITICAL | **Category**: backend
> **Anti-Pattern Warning**: Implicit structured cloning of binary payloads and post-transfer access to detached ArrayBuffers

## System Constraints
You are a Principal Engineer enforcing zero-copy memory invariants across Bun 1.2 clustered worker threads. In Bun, transferring binary data without an explicit transfer list defaults to structured clone serialization, imposing severe heap overhead and latency spikes. Furthermore, transferring an ArrayBuffer causes immediate detachment in the sender thread; any subsequent read or write triggers runtime exceptions or silent zeroes. You must mandate transfer list passing, immediate reference nullification, detachment assertions, or SharedArrayBuffer usage where appropriate.

## Strict Guidelines
- Engineers MUST ALWAYS pass underlying ArrayBuffers in the transferList parameter: `worker.postMessage(message, [buffer])`.
- Engineers MUST IMMEDIATELY nullify or discard local references to transferred ArrayBuffers/TypedArrays after dispatching to prevent post-detachment access.
- Engineers MUST NOT rely on structured clone fallback for ArrayBuffer or TypedArray instances in high-frequency messaging pipelines.
- Code MUST verify `buffer.detached` (or `buffer.byteLength === 0`) when handling potentially transferred buffers defensively.
- Services MUST use `SharedArrayBuffer` coupled with `Atomics` if concurrent non-destructive read/write access is required across threads without transferring ownership.
- Components NEVER re-use a TypedArray slice without transferring the underlying `buffer.slice(...)` or transferring the root `buffer` entirely.

## Bad vs Good Implementations
### Zero-Copy Transfer with Immediate Detachment Handling

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Failing to pass chunk.buffer in postMessage's transfer list forces Bun's JavaScriptCore to perform a deep structured copy of the buffer on the heap. If partially transitioned to zero-copy without removing downstream references, reading chunk.byteLength or mutating chunk will operate on a detached buffer (byteLength === 0).
```typescript
import { Worker } from 'bun';

const worker = new Worker(new URL('./ingest-worker.ts', import.meta.url));

export function dispatchChunk(chunk: Uint8Array): void {
  // Anti-pattern: Missing transferList causes full structured cloning copy
  worker.postMessage({ type: 'CHUNK', payload: chunk });

  // Anti-pattern: Accessing buffer after assuming ownership was transferred
  // In a refactor where transferList is partially added, this causes use-after-detachment
  console.log(`Dispatched byteLength: ${chunk.byteLength}`);
}
```

#### Production Standard (Correct)
> **Standard**: Explicitly passing `[buffer]` transfers ownership across Bun worker boundaries in O(1) time without memory copying. Capturing metrics prior to dispatch and immediately nullifying the sender's reference ensures zero-copy throughput and prevents post-detachment reads or writes.
```typescript
import { Worker } from 'bun';

const worker = new Worker(new URL('./ingest-worker.ts', import.meta.url));

export function dispatchChunk(chunk: Uint8Array): void {
  const buffer = chunk.buffer;
  const byteLength = chunk.byteLength;

  // Enforce zero-copy transfer by moving ownership of the ArrayBuffer
  worker.postMessage(
    { type: 'CHUNK', payload: chunk, byteLength },
    [buffer]
  );

  // Invariant: buffer is now detached in this thread (buffer.detached === true)
  // Invalidate reference immediately to prevent use-after-free / detached access
  chunk = null as unknown as Uint8Array;
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Bun Runtime Inspector MCP
Inspects running Bun threads, heap allocations, and worker postMessage channel metrics.
Recommended Agent Skills (askills.dev)

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

Bun Memory & CPU Profiler
Runs Bun native CPU and heap sampling to detect structured clone allocations in worker thread boundaries.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Bun 1.2 Clustered Worker Zero-Copy ArrayBuffer Transfer Guardrail

Bun 1.2 Clustered Worker Zero-Copy ArrayBuffer Transfer Guardrail defines an industrial-grade behavioral standard for backend engineering. Enforces explicit ownership transfer semantics and detachment verification for ArrayBuffer payloads sent across Bun worker threads. Eliminates multi-gigabyte structured clone serialization overhead and prevents invalid memory reads on detached ArrayBuffers under extreme messaging throughput. 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 cloning of binary payloads and post-transfer access to detached ArrayBuffers 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 cloning of binary payloads and post-transfer access to detached ArrayBuffersCritical
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 underlying ArrayBuffers in the transferList parameter

Engineers MUST ALWAYS pass underlying ArrayBuffers in the transferList parameter: `worker.postMessage(message, [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.
2

Engineers MUST IMMEDIATELY nullify or discard local references to transferred ArrayBuffers/TypedArrays after dispatching to prevent post-detachment access.

Engineers MUST IMMEDIATELY nullify or discard local references to transferred ArrayBuffers/TypedArrays after dispatching to prevent post-detachment access.

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 NOT rely on structured clone fallback for ArrayBuffer or TypedArray instances in high-frequency messaging pipelines.

Engineers MUST NOT rely on structured clone fallback for ArrayBuffer or TypedArray instances in high-frequency messaging pipelines.

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 MUST verify `buffer.detached` (or `buffer.byteLength === 0`) when handling potentially transferred buffers defensively.

Code MUST verify `buffer.detached` (or `buffer.byteLength === 0`) when handling potentially transferred buffers defensively.

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` coupled with `Atomics` if concurrent non-destructive read/write access is required across threads without transferring ownership.

Services MUST use `SharedArrayBuffer` coupled with `Atomics` if concurrent non-destructive read/write access is required across threads without transferring ownership.

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 re-use a TypedArray slice without transferring the underlying `buffer.slice(...)` or transferring the root `buffer` entirely.

Components NEVER re-use a TypedArray slice without transferring the underlying `buffer.slice(...)` or transferring the root `buffer` entirely.

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 ArrayBuffer Transfer Guardrail critical for AI coding assistants?

Enforces explicit ownership transfer semantics and detachment verification for ArrayBuffer payloads sent across Bun worker threads. Eliminates multi-gigabyte structured clone serialization overhead and prevents invalid memory reads on detached ArrayBuffers under extreme messaging throughput. 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 cloning of binary payloads and post-transfer access to detached ArrayBuffers) 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