forge docs

Python Identity

This page shows Identity from the Python SDK perspective. The shared Forge contract still applies, but examples, package boundaries, verification commands, and deployment expectations should be read through orchestration, data workflows, ML-adjacent systems, retrieval, and automation.

Language context

  • Primary package surface: forge-sdk
  • Install entry point: pip install forge-sdk
  • Verification command: PYTHONPATH=src pytest
  • Shared contract reference: Identity

Python workflows should keep data, embeddings, tools, and provider calls inside the same accountable runtime model.

Subject in Python

For Python, focus on did:oas roots, lineage, glyphs, signatures, and production-safe key material handling. 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 Python 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 PYTHONPATH=src pytest before claiming behavior is ready.
  5. Run python3 tools/release_gate.py --root . before release work.
pip install forge-sdk
PYTHONPATH=src pytest