Solutions Overview
Use this page to select the correct public Verdictan workflow. Start with the active task.
If the workflow has a specified field, command, or contract, use the linked references.
Select your path
| Outcome | Start here | Then go deeper into |
|---|---|---|
| Get a governed gateway running. | Read Quickstart. | Read Install the Gateway and CLI Overview. |
| Roll out a config-led operating model. | Read Config-First Workflow. | Read Configurations and Declarative Config Reference. |
| Standardize provider access with your own keys. | Read Providers and BYOK Routing. | Read Managing API Tokens and Usage Costs and Budgets. |
| Control cost and access. | Read Usage Costs and Budgets. | Read API Token Management and verdictan spend. |
| Investigate blocked or escalated traffic. | Read Investigate a Blocked Request. | Read Resolve an Escalation and Debugging Requests. |
| Create review evidence. | Read Export Evidence for a Review. | Read verdictan export-jobs and Reviewing Alerts and Evidence. |
Know when the outcome is complete
| Outcome | Verification checkpoint |
|---|---|
| Governed gateway running | /healthz succeeds. An authenticated request gets a response from a configured model through the gateway. |
| Configuration rolled out | The config lints, its pack tests pass, and the specified configuration is the one applied to the target gateway. |
| BYOK provider access active | The organization credential resolves and the simulation returns ready_byok. The specified endpoint accepts the request. |
| Block or escalation investigated | The record has a request ID, decisive policy or routing result, and configuration context. It also has a named next action. |
| Evidence package complete | The export job completed. The file includes the specified time window. The handoff contains the related request or escalation IDs. |
Process health, schema validation, policy simulation, and a model request prove different things. One checkpoint is not a replacement for the others.
Use paths together intentionally
- After you understand the gateway and credential boundaries, use an integration guide. Provider setup does not replace the core quickstart.
- Pair configuration rollout with the investigation workflow so operators know how to verify an unexpected change and apply a rollback.
- Pair BYOK provider setup with token and budget guidance. Stored access-policy and budget-policy simulations show specified decisions. They do not prove live enforcement.
- Use the evidence workflow for a reviewable handoff, not as a replacement for finding the cause of the underlying request.
Next steps
- Read Quickstart.
- Read Config-First Workflow.
- Read Providers and BYOK Routing.
- Read Export Evidence for a Review.