Skip to main content
Version: 1.8.0

DVARA cookbook

Use these recipes when one task crosses several parts of the DVARA AI governance platform. Each recipe starts with its prerequisites, shows the configuration or request, and ends with evidence you can check.

The recipes describe the 1.8 product contract. Use the DVARA examples repository for runnable applications, but check an example's release notes before using it with a different DVARA version.

Choose the right kind of guide​

You want to …Read this
Understand how the platform fits togetherArchitecture
Register and test one model providerProvider setup
Connect a language SDK or frameworkIntegrations
Configure one governance controlGovernance
Complete a task that crosses several controlsThe recipes below

Pick a 1.8 recipe​

TaskDistribution boundaryWhat you verify
Add DVARA to an existing OpenAI SDK application—The application reaches DVARA, the request receives a trace ID, and configured governance runs
Canary a provider change and roll backConfiguration workflow differsBaseline and candidate traffic use the intended split and rollback returns the candidate share to zero
Attribute cost per workspaceEnterprise onlyUsage and available provider pricing produce workspace cost records and a chargeback report
Stream Chat Completions end to end—The client handles SSE chunks, structured output accumulation, governance endings, and retry boundaries

The cost-attribution recipe is not an Open Source workflow. Open Source exposes request metrics and local audit output, but it does not include Flightdeck, persistent workspace cost records, or the chargeback report.

Check the contract behind a recipe​

Use the task recipe for the sequence, then follow its links to the canonical reference for field names, defaults, edition boundaries, and error behavior. This keeps one source of truth for each control instead of repeating reference tables in the cookbook.

If a task is missing, open a documentation issue with the outcome you need and the distribution you run.