| name | native-ios-core |
| description | Shared reference for the native-iOS cluster: the iOS 26 / Swift 6.2 / Xcode 26 baseline, availability-gating discipline for the new frameworks, the data-race-safety (actor isolation + Sendable) model, and shared SwiftUI conventions. USE WHEN adopting Swift 6.2 concurrency, gating an iOS 26-only API, or choosing a state/persistence pattern — the rules every native-iOS spoke shares. |
| cluster | native-ios |
| version | 1.0.0 |
Native iOS Core
Shared model for the native-ios cluster. The concurrency, SwiftUI, persistence, AI, and design
spokes all depend on the same baseline and the same safety rules — keep them consistent here so no
spoke contradicts another.
1. The baseline (this cluster's defining decision)
Everything is written for one toolchain line:
Xcode 26 ──compiles──> Swift 6.2 ──targets──> iOS 26 / macOS 26 (with graceful fallback below)
The flagship capabilities the cluster exists to teach — Approachable Concurrency, Liquid
Glass, and on-device FoundationModels — only exist on this line. So the first question for
any task is "what's the deployment target, and is this API available there?" — not "how do I
call it?". Get the baseline right and the spokes compose; get it wrong and they conflict.
2. Availability gating (non-negotiable)
A higher SDK does not mean every device can run the API. Gate, don't assume:
