forge docs

Swift Deployment

This page shows Deployment from the Swift SDK perspective. The shared Forge contract still applies, but examples, package boundaries, verification commands, and deployment expectations should be read through iOS, macOS, local identity, native approval flows, and Apple-platform UX.

Language context

  • Primary package surface: ForgeSDK
  • Install entry point: swift package add ForgeSDK
  • Verification command: swift test
  • Shared contract reference: Deployment

Swift integrations should make local identity, user consent, and approval state visible in native UX.

Subject in Swift

For Swift, focus on local execution, WASI modules, containers, edge targets, Aut0 positions, and Sigil evidence paths. Treat this page as the language-specific entry point, then use the shared contract page when you need the cross-language rule text.

Implementation checklist

  1. Start with the Swift package boundary rather than copying examples from another SDK.
  2. Keep OAS identity and Arsenal capability checks visible in the code path.
  3. Use provider names through Forge's namespace contract instead of hard-coding vendors.
  4. Run swift test before claiming behavior is ready.
  5. Run python3 tools/release_gate.py --root . before release work.
swift package add ForgeSDK
swift test