AgentRules.org
RulesStacksClientsAuditorPrunerSelf-HealRFCsBenchmarkCLICI/CDAuthorsSubmit
This specification is maintained by the AgentRules Working Group. Have enhancements or want to claim maintainership?Submit Specification →
mobilecritical PriorityID: kmp-swift-interop-memory-isolation-guardrail

Kotlin Multiplatform Swift-Interop Memory Isolation and Deterministic Ownership Fences

Governs boundary crossings between Kotlin/Native GC and Apple Swift ARC runtimes. Mandates explicit ownership transfer fences, deterministic unpinning of bridged references via paired disposable tokens, and weak capture semantics across runtime boundaries to eliminate native heap leaks.

Prohibited Anti-Pattern: Leaking Kotlin Native Objects Across Swift Interop via Unfenced Bridging and Orphaned Retain Cycles

Export Ready-to-Drop Configuration

Select format below to copy code or download file directly.

---
description: Kotlin Multiplatform Swift-Interop Memory Isolation and Deterministic Ownership Fences - Governs boundary crossings between Kotlin/Native GC and Apple Swift ARC runtimes. Mandates explicit ownership transfer fences, deterministic unpinning of bridged references via paired disposable tokens, and weak capture semantics across runtime boundaries to eliminate native heap leaks.
globs: **/*.kt, **/*.swift, iosApp/**/*.swift
alwaysApply: true
verified_by: "agentrules.org"
license: "CC-BY-4.0"
source: "https://agentrules.org/rules/kmp-swift-interop-memory-isolation-guardrail"
---

# Kotlin Multiplatform Swift-Interop Memory Isolation and Deterministic Ownership Fences

> **Severity**: CRITICAL | **Category**: mobile
> **Anti-Pattern Warning**: Leaking Kotlin Native Objects Across Swift Interop via Unfenced Bridging and Orphaned Retain Cycles

## System Constraints
You are a Principal Mobile Architect enforcing strict memory isolation and deterministic ownership transfer between Kotlin/Native and Apple Swift runtimes. You must enforce explicit unpinning, lifecycle fencing, and weak delegate decoupling to prevent native heap corruption and silent memory leaks.

## Strict Guidelines
- Engineers MUST ALWAYS pair every explicit `StableRef.create()` invocation with an unambiguous, deterministic cleanup fence (`dispose()`) invoked in the corresponding Swift `deinit` or managed scope.
- Engineers MUST NOT pass raw Kotlin closure callbacks or long-lived delegates to Swift without wrapping the receiver in an explicit weak capture or scoped bridge token.
- Code SHOULD expose an explicit `Disposable` or `Closeable` interface across the interop boundary for any Kotlin state-holder referenced by Swift ViewModels or Coordinators.
- Services MUST invalidate cross-runtime listener subscriptions during lifecycle teardown (e.g., `deinit` in Swift, or `onCleared()` in Kotlin).
- Components NEVER store direct strong references to Swift UI instances (`UIViewController`, `UIView`) inside Kotlin singletons or long-lived coroutine scopes.

## Bad vs Good Implementations
### Deterministic Cross-Runtime Ownership Fence in Swift-KMP Consumer

#### Bad Antipattern (AI Common Hallucination)
> **Why it fails**: Strong capture of self in the interop closure combined with retaining the Kotlin subscription handle creates a cyclic retain path between Swift ARC and Kotlin/Native runtime. Swift deinit is never invoked, leaving the underlying Kotlin object permanently pinned on the native heap.
```swift
final class SwiftDataConsumer {
    private var kotlinSubscription: KotlinSubscriptionHandle?

    func bind(to producer: KotlinDataProducer) {
        // ANTI-PATTERN: Strong capture across runtime boundary creates invisible ARC/GC retain cycle
        self.kotlinSubscription = producer.subscribe { data in
            self.handleUpdate(data)
        }
    }
    // No deinit unpinning: Kotlin Native object remains rooted indefinitely in heap
}
```

#### Production Standard (Correct)
> **Standard**: Explicit [weak self] capture prevents cross-runtime retain cycles. Implementing deterministic release inside deinit via DisposableHandle.dispose() signals the Kotlin/Native memory manager that the interop reference can be safely collected.
```swift
final class SwiftDataConsumer {
    private var kotlinSubscription: DisposableHandle?

    func bind(to producer: KotlinDataProducer) {
        // PRODUCTION INVARIANT: Weak capture breaks ARC cycle; deterministic handle pinned
        self.kotlinSubscription = producer.subscribe { [weak self] data in
            guard let self = self else { return }
            self.handleUpdate(data)
        }
    }

    deinit {
        // Explicit ownership fence: Unpin Kotlin reference from Swift lifecycle
        kotlinSubscription?.dispose()
        kotlinSubscription = nil
    }
}
```
Recommended MCP Servers (mcp-serverlist.com)

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

Xcode Instruments Leaks Inspector
Monitors native heap allocations and detects retained Kotlin/Native bridge pointers in Apple runtime processes.
Recommended Agent Skills (askills.dev)

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

KMP Swift Interop Static Analyzer
Analyzes Swift and Kotlin boundary code to verify closure weak-capture semantics and paired disposable invocations.
Architectural Specification & Invariant Rationale

Architectural Invariant Design: Kotlin Multiplatform Swift-Interop Memory Isolation and Deterministic Ownership Fences

Kotlin Multiplatform Swift-Interop Memory Isolation and Deterministic Ownership Fences defines an industrial-grade behavioral standard for mobile engineering. Governs boundary crossings between Kotlin/Native GC and Apple Swift ARC runtimes. Mandates explicit ownership transfer fences, deterministic unpinning of bridged references via paired disposable tokens, and weak capture semantics across runtime boundaries to eliminate native heap leaks. 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: Leaking Kotlin Native Objects Across Swift Interop via Unfenced Bridging and Orphaned Retain Cycles 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 DriftLeaking Kotlin Native Objects Across Swift Interop via Unfenced Bridging and Orphaned Retain CyclesCritical
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 pair every explicit `StableRef.create()` invocation with an unambiguous, deterministic cleanup fence (`dispose()`) invoked in the corresponding Swift `deinit` or managed scope.

Engineers MUST ALWAYS pair every explicit `StableRef.create()` invocation with an unambiguous, deterministic cleanup fence (`dispose()`) invoked in the corresponding Swift `deinit` or managed scope.

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 pass raw Kotlin closure callbacks or long-lived delegates to Swift without wrapping the receiver in an explicit weak capture or scoped bridge token.

Engineers MUST NOT pass raw Kotlin closure callbacks or long-lived delegates to Swift without wrapping the receiver in an explicit weak capture or scoped bridge token.

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 SHOULD expose an explicit `Disposable` or `Closeable` interface across the interop boundary for any Kotlin state-holder referenced by Swift ViewModels or Coordinators.

Code SHOULD expose an explicit `Disposable` or `Closeable` interface across the interop boundary for any Kotlin state-holder referenced by Swift ViewModels or Coordinators.

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 invalidate cross-runtime listener subscriptions during lifecycle teardown (e.g., `deinit` in Swift, or `onCleared()` in Kotlin).

Services MUST invalidate cross-runtime listener subscriptions during lifecycle teardown (e.g., `deinit` in Swift, or `onCleared()` in Kotlin).

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 store direct strong references to Swift UI instances (`UIViewController`, `UIView`) inside Kotlin singletons or long-lived coroutine scopes.

Components NEVER store direct strong references to Swift UI instances (`UIViewController`, `UIView`) inside Kotlin singletons or long-lived coroutine scopes.

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 Kotlin Multiplatform Swift-Interop Memory Isolation and Deterministic Ownership Fences critical for AI coding assistants?

Governs boundary crossings between Kotlin/Native GC and Apple Swift ARC runtimes. Mandates explicit ownership transfer fences, deterministic unpinning of bridged references via paired disposable tokens, and weak capture semantics across runtime boundaries to eliminate native heap leaks. 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 (Leaking Kotlin Native Objects Across Swift Interop via Unfenced Bridging and Orphaned Retain Cycles) 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 MOBILE Rules

View all rules →
mobile
106

Tauri 2.0 Mobile IPC & Capabilities Permissions Matrix Standard

Tauri v2 introduces a capability-driven permissions system replacing legacy v1 allowlists across iOS and Android runtimes. Failure to constrain IPC command handlers with typed schemas and explicit mobile capability definitions exposes native mobile OS surfaces to arbitrary code execution, permission leakage, and silent serialization failures. Production mobile deployments require strictly typed IPC boundary validation, granular capability scopes, and graceful permission degradation.

mobile
70

Capacitor 7 Native Bridge, Biometric Auth & Android 15 Lifecycle Production Standard

Capacitor 7 enforces strict bridge lifecycle contracts, asynchronous native plugin interop, and mandatory Android 15 edge-to-edge window inset handling. Storing sensitive authentication tokens in unencrypted web storage or failing to bind biometric authentication directly to hardware-backed Keystore or Secure Enclave mechanisms compromises app integrity and causes fatal crash or viewport occlusion issues on modern mobile operating systems.

mobile
58

Tauri 2.0 Mobile IPC Isolation and Capabilities Permission Scoping

Enforces strict capability permission boundaries, payload validation, and secure IPC invoke scoping for Tauri v2 Android and iOS environments. Prevents arbitrary IPC command execution, excessive native privilege granting, and deserialization vulnerabilities across the mobile webview-native boundary.

1 Rule in Stack

Kotlin