Go GORM Concurrency & Transaction Safety Standard

--- description: Go GORM Concurrency & Transaction Safety Standard - Guardrails for Go GORM: prevent race conditions on shared DB handles, use db.WithContext(ctx), and encapsulate multi-step mutations in db.Transaction. globs: **/*.go alwaysApply: true verified_by: "agentrules.org" license: "CC-BY-4.0" source: "https://agentrules.org/rules/go-gorm-concurrency" --- # Go GORM Concurrency & Transaction Safety Standard > **Severity**: CRITICAL | **Category**: backend > **Anti-Pattern Warning**: AI reuses a mutated *gorm.DB instance across goroutines, causing race conditions and cross-polluted queries. ## System Constraints You are a Golang database engineer using GORM. A *gorm.DB instance is not thread-safe if modified with conditions. Always obtain a session with db.WithContext(ctx) for every goroutine or HTTP request. Wrap multi-step mutations inside db.Transaction. ## Strict Guidelines - Always initialize a fresh context session: `tx := db.WithContext(ctx)` before chaining queries. - Never share a scoped *gorm.DB handle across multiple concurrent goroutines. - Use `db.Transaction(func(tx *gorm.DB) error { ... })` for ACID guarantees on multi-write operations. ## Bad vs Good Implementations ### Safe GORM Transaction with Context #### Bad Antipattern (AI Common Hallucination) > **Why it fails**: Lack of transaction causes money loss if the second update fails or connection drops. ```go // Anti-pattern: Mutating shared DB without context or transaction func TransferFunds(fromID, toID uint, amount int64) error { db.Model(&Account{}).Where("id = ?", fromID).Update("balance", gorm.Expr("balance - ?", amount)) // If server crashes here, funds are lost forever! db.Model(&Account{}).Where("id = ?", toID).Update("balance", gorm.Expr("balance + ?", amount)) return nil } ``` #### Production Standard (Correct) > **Standard**: Atomically commits or rolls back both operations inside an isolated transaction with context. ```go // Production Standard: Atomic transaction with context func TransferFunds(ctx context.Context, db *gorm.DB, fromID, toID uint, amount int64) error { return db.WithContext(ctx).Transaction(func(tx *gorm.DB) error { if err := tx.Model(&Account{}).Where("id = ? AND balance >= ?", fromID, amount). Update("balance", gorm.Expr("balance - ?", amount)).Error; err != nil { return err } if err := tx.Model(&Account{}).Where("id = ?", toID). Update("balance", gorm.Expr("balance + ?", amount)).Error; err != nil { return err } return nil }) } ```

Architectural Specification & Invariant Rationale

Architectural Invariant Design: Go GORM Concurrency & Transaction Safety Standard

Go GORM Concurrency & Transaction Safety Standard defines an industrial-grade behavioral standard for backend engineering. Guardrails for Go GORM: prevent race conditions on shared DB handles, use db.WithContext(ctx), and encapsulate multi-step mutations in db.Transaction. 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: AI reuses a mutated *gorm.DB instance across goroutines, causing race conditions and cross-polluted queries. 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	AI reuses a mutated *gorm.DB instance across goroutines, causing race conditions and cross-polluted queries.	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:

Always initialize a fresh context session

Always initialize a fresh context session: `tx := db.WithContext(ctx)` before chaining queries.

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.

Never share a scoped *gorm.DB handle across multiple concurrent goroutines.

Enforcement:Integrated into the Agent Pack rule file. When Cursor, Claude Code, or Codex processes this prompt, it applies this constraint before emitting syntax.

Use `db.Transaction(func(tx *gorm.DB) error { ... })` for ACID guarantees on multi-write operations.

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 Go GORM Concurrency & Transaction Safety Standard critical for AI coding assistants?

Guardrails for Go GORM: prevent race conditions on shared DB handles, use db.WithContext(ctx), and encapsulate multi-step mutations in db.Transaction. 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 (AI reuses a mutated *gorm.DB instance across goroutines, causing race conditions and cross-polluted queries.) 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.