Skip to main content

Architecture Overview

Your application sends model requests through Verdictan. The gateway controls request routing. It applies policy to request families that use its policy evaluation path. Product surfaces show rollout state, request events, captured session history, audit records, human-review work, and spend.

Public component model​

What each component owns​

ComponentPublic responsibility
Your applicationSends requests and consumes responses
Verdictan gatewayAuthenticates and routes supported requests, applies policy on policy-covered routes, and emits outcomes for each route that the runtime implements
Model providerCreates the upstream model response
Product surfacesHelp teams review rollout state, request events, capture-enabled session history, human-review queues, audit records, and spend

Policy-covered request flow​

Chat Completions, Responses, and Messages use this policy-covered flow. Each family keeps its own request and response shape.

The Anthropic-shaped POST /v1/messages route uses the shared access, input, tool, output, and audit stages. WebSocket routes authenticate the connection and apply policy to complete text frames. They reject binary frames and malformed JSON-like text. Request shapes have different capability limits. See Runtime Request Families and Streaming with SSE.

Customer-facing surfaces​

  • Configurations and Templates manage versioned policy changes.
  • Gateways shows runtime inventory and the state of connected gateways.
  • Overview summarizes aggregate traffic and governance activity. It is not a request-detail view.
  • verdictan events and GET /v1/events must include the since query. They expose request IDs, outcomes, configuration versions, and policy evidence.
  • History shows captured session context if history capture is enabled. The capture mode and platform retention policy control the available metadata or content.
  • Inbox handles human-review work such as escalations and approvals.
  • Trail is the audit and evidence surface, including export workflows.
  • Usage and Budgets include spend analysis and cost-governance state.

Public boundaries​

  • Your application points at the Verdictan gateway. It does not call the provider directly.
  • Runtime behavior is defined through declarative config such as policy-config.yaml.
  • Secret material is not in YAML and is referenced through secret_key_ref.

Next steps​