forge docs

Kotlin Deployment

This page shows Deployment from the Kotlin SDK perspective. The shared Forge contract still applies, but examples, package boundaries, verification commands, and deployment expectations should be read through Android, JVM services, mobile agents, and Kotlin-first product stacks.

Language context

  • Primary package surface: ai.l1fe:forge-kt
  • Install entry point: implementation("ai.l1fe:forge-kt")
  • Verification command: ./gradlew test
  • Shared contract reference: Deployment

Kotlin integrations should keep Android-local concerns separate from JVM service deployment concerns.

Subject in Kotlin

For Kotlin, 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 Kotlin 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 ./gradlew test before claiming behavior is ready.
  5. Run python3 tools/release_gate.py --root . before release work.
implementation("ai.l1fe:forge-kt")
./gradlew test