forge docs

Go Providers

This page shows Providers from the Go SDK perspective. The shared Forge contract still applies, but examples, package boundaries, verification commands, and deployment expectations should be read through cloud-native services, gateways, platform backends, and operational runtimes.

Language context

  • Primary package surface: forge-go
  • Install entry point: go get forge.l1fe.ai/sdk
  • Verification command: go test ./...
  • Shared contract reference: Providers

Go integrations should make lifecycle, health, context propagation, and deployment boundaries explicit.

Subject in Go

For Go, focus on namespace:implementation routing, credentials, model capability metadata, streaming, and provider telemetry. 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 Go 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 go test ./... before claiming behavior is ready.
  5. Run python3 tools/release_gate.py --root . before release work.
go get forge.l1fe.ai/sdk
go test ./...