Architectural Invariant Design: KMP SKIE Flow-to-AsyncSequence Backpressure & Bounded Buffer Guardrail
KMP SKIE Flow-to-AsyncSequence Backpressure & Bounded Buffer Guardrail defines an industrial-grade behavioral standard for mobile engineering. Enforces strict bounded buffering and explicit overflow policies on Kotlin Multiplatform Flows exposed to Swift via SKIE. Without explicit backpressure boundaries, mismatched production-consumption rates across the Kotlin/Native and Swift async boundary cause unmonitored queue accumulation, rapid heap exhaustion, and iOS Jetsam terminations during high-frequency streaming. Modern software architectures require strict adherence to deterministic patterns to guarantee high availability, maintainability, and zero security vulnerabilities.
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 | Unbounded Flow Bridging to Swift AsyncSequence Triggering Uncontrolled Memory Growth and Jetsam Kills | 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. |
Step-by-Step Production Directives
Each rule constraint below is injected into the AI agent's system prompt to establish deterministic boundaries:
Engineers MUST ALWAYS declare an explicit bounded buffer strategy (via .buffer() or SharedFlow replay/extraBufferCapacity) with a designated BufferOverflow policy (DROP_OLDEST or DROP_LATEST) on any Flow exported to Swift via SKIE.
Engineers MUST ALWAYS declare an explicit bounded buffer strategy (via .buffer() or SharedFlow replay/extraBufferCapacity) with a designated BufferOverflow policy (DROP_OLDEST or DROP_LATEST) on any Flow exported to Swift via SKIE.
Engineers MUST NOT expose raw unbounded channelFlow, callbackFlow, or default MutableSharedFlow instances directly to iOS consumers without wrapping them in a bounded operator.
Engineers MUST NOT expose raw unbounded channelFlow, callbackFlow, or default MutableSharedFlow instances directly to iOS consumers without wrapping them in a bounded operator.
Engineers MUST ensure Swift consumers manage lifecycle-scoped Task cancellation, preventing zombie subscriptions from hanging Kotlin CoroutineScope instances across the Darwin runtime boundary.
Engineers MUST ensure Swift consumers manage lifecycle-scoped Task cancellation, preventing zombie subscriptions from hanging Kotlin CoroutineScope instances across the Darwin runtime boundary.
High-frequency event streams (e.g., location, BLE telemetry, real-time WebSockets) MUST specify a maximum buffer capacity not exceeding 64 items unless an explicit high-capacity ring-buffer architecture is formally documented.
High-frequency event streams (e.g., location, BLE telemetry, real-time WebSockets) MUST specify a maximum buffer capacity not exceeding 64 items unless an explicit high-capacity ring-buffer architecture is formally documented.
Code SHOULD leverage SKIE's native cancellation propagation by pairing Task cancellation in SwiftUI (.task modifier) with cooperative CoroutineScope cancellation in Kotlin.
Code SHOULD leverage SKIE's native cancellation propagation by pairing Task cancellation in SwiftUI (.task modifier) with cooperative CoroutineScope cancellation in Kotlin.
Services MUST NEVER rely on Swift's AsyncSequence consumer consumption rate to backpressure native Kotlin upstream emitters without explicit cooperative suspension verification.
Services MUST NEVER rely on Swift's AsyncSequence consumer consumption rate to backpressure native Kotlin upstream emitters without explicit cooperative suspension verification.
Frequently Asked Technical Questions
Common questions developers face when configuring AI coding assistants for this stack:
Q:Why is KMP SKIE Flow-to-AsyncSequence Backpressure & Bounded Buffer Guardrail critical for AI coding assistants?
Enforces strict bounded buffering and explicit overflow policies on Kotlin Multiplatform Flows exposed to Swift via SKIE. Without explicit backpressure boundaries, mismatched production-consumption rates across the Kotlin/Native and Swift async boundary cause unmonitored queue accumulation, rapid heap exhaustion, and iOS Jetsam terminations during high-frequency streaming. 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 (Unbounded Flow Bridging to Swift AsyncSequence Triggering Uncontrolled Memory Growth and Jetsam Kills) 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.