generated: '2026-07-18'
method: derived
source: openapi/armada-orchestrator-openapi-original.yml
# Cross-cutting standards conformance, derived from the Orchestrator OpenAPI plus
# published docs. No third-party compliance certifications (SOC 2 / ISO 27001 / etc.)
# were found published, so no `Compliance` pointer is emitted.
standards:
  - id: openapi-3.0
    conforms: true
    evidence: openapi 3.0.3 document published at docs.armada.ai/openapi/v1/orchestrator.yaml
  - id: http-bearer-jwt
    conforms: true
    evidence: components.securitySchemes.bearerAuth type http scheme bearer bearerFormat JWT, applied globally
  - id: oidc
    conforms: true
    evidence: console.armada.ai sign-in is OIDC via Keycloak (login docs; realm-backed)
  - id: oauth2
    conforms: false
    evidence: no oauth2 securityScheme declared; auth is opaque/JWT bearer, not an oauth2 flow
  - id: rfc9457-problem-details
    conforms: false
    evidence: error responses use plain HTTP status codes, no application/problem+json media type
  - id: openai-chat-completions
    conforms: true
    evidence: Bridge AI Studio Model-as-a-Service exposes OpenAI-compatible /v1/chat/completions