Swift

TeaQL Swift generates typed entities, requests, expressions, audited mutations, a passive GeneratedRuntimeModule.module, and ten Assist categories. The currently verified database path is SQLite. Query terminals take one UserContext parameter named context; executeForList(context) returns SmartList<Entity>, while save(context) returns the persisted typed entity.

Start with the Quick Start, prove the real SQLite path with First Verification, continue with Scenarios, and keep application-owned wiring in Customization. For AI-assisted work, use the TeaQL Agent Kit harness with the generated Assist files. Use Swift Debugging and Observability to capture safe SQL evidence and verify staged relations, analytics, audited saves, telemetry, and tenant guards.

Runtime Module installation is passive. Call schema reconciliation explicitly; telemetry remains optional and uses a no-op implementation unless the application installs OpenTelemetry support.

Evidence boundary

Use Latest Versions for the current tag and generator-selected dependency. Use Cross-language Conformance Status for the committed capability/evidence snapshot. SQLite is the verified provider path described by this guide; neither a generated target nor a published tag alone asserts broader provider or support coverage.