Skip to main content

Customer Journeys

These journeys show how customers move through Verdictan after access is available. Use them for a task-oriented map. Do not use them as a page-by-page product tour.

Examine individual runtime requests with verdictan events tail or GET /v1/events. Set the since query. The console Overview summarizes aggregate activity. It does not replace request-level event lookup. History adds session context only for capture-enabled flows.

Journey map​

Getting live​

JourneyStarts hereSuccess signal
Evaluate quicklyQuickstartThe client succeeds and the event query returns the matching request ID
Run a connected gatewayInstall the GatewayA connected runtime is healthy in Gateways
Set up team ownershipOnboarding TeamsAccess, review, and billing owners are clear

Operate​

JourneyStarts hereSuccess signal
Roll out a policy changeConfigurationsNew version is deployed and behaves as specified
Investigate an unexpected decisionverdictan eventsRoot cause and next action are clear
Review human-review workInboxReview item is claimed, resolved, rejected, or returned to the shared queue
Export evidence for a reviewTrailEvidence package is available for handoff

Govern spend​

JourneyStarts hereSuccess signal
Review spend and budgetsUsageThe team can show the causes of recent spend and budget actions

Journey 1: Evaluate quickly​

  1. Finish Quickstart.
  2. Send a representative governed request.
  3. Run verdictan events tail --since 10m --json and verify the request ID and governance outcome.
  4. If conversation capture is enabled, verify the request in History.
  5. Open Overview and verify that the organization shows live activity.

Use this journey for evaluations, prototypes, and first-time product walkthroughs.

Journey 2: Run a connected gateway​

  1. Install verdictan using Install the Gateway.
  2. Start the runtime with verdictan gateway run.
  3. Verify that Gateways shows the runtime.
  4. Send a governed request and verify its request ID and outcome with verdictan events tail --since 10m --json.
  5. If conversation capture is enabled for the flow, verify the captured session in History.

Use this journey when your organization runs the runtime in its own infrastructure perimeter.

Journey 3: Set up team ownership​

  1. Invite members and assign roles.
  2. Record who owns policy rollout, inbox review, audit exports, and billing controls.
  3. Verify that each person can open only the surfaces specified for their role.
  4. Review Onboarding Teams for the operating checklist.

Use this journey when moving from a single-user evaluation to a shared organization.

Journey 4: Roll out a policy change​

  1. Start from a template or a saved configuration.
  2. Validate the YAML locally.
  3. Save or review the change in Configurations.
  4. Deploy to the target gateway.
  5. Verify runtime state in Gateways.
  6. Verify representative traffic with verdictan events tail --since 10m --json or GET /v1/events?since=10m.
  7. If conversation capture is enabled, examine History.
  8. If review volume can change, monitor Inbox.

Use this journey for controlled rollout of policy, routing, or provider changes.

Journey 5: Investigate an unexpected decision​

  1. Query verdictan events tail --since <window> --json or GET /v1/events?since=<window>.
  2. Find the matching request ID.
  3. If conversation capture is enabled, use History for the captured session context.
  4. Review the verdict, policy results, provider details, and timestamps.
  5. Compare the request with the active configuration version.
  6. Open Trail for audit chronology or an evidence export.
  7. Identify if the result agrees with the active policy, shows a tuning issue, or shows a broader incident.

Use this journey for day-to-day support, rollout follow-up, and incident triage.

Journey 6: Review human-review work​

  1. Open Inbox and filter to the related review category.
  2. Claim the item when you are actively working it.
  3. Review the linked request context.
  4. If capture is enabled, compare the captured session in History.
  5. If capture is disabled, use the linked event and request metadata.
  6. Resolve or reject the item, or return it to the shared queue with Unclaim.

Use this journey when Verdictan creates an escalation or approval task.

Journey 7: Export evidence for a review​

  1. Open Trail and switch to the evidence export view.
  2. Select the time window.
  3. Select the export format.
  4. Select Request export job and wait while the job is queued or processing.
  5. When the job is completed, download the export.
  6. Make sure that the date range and scope are correct.
  7. Pair the file with the related request IDs, incident ID, or review note.

Use this journey for audits, compliance reviews, customer investigations, and incident response.

Journey 8: Review spend and budgets​

  1. Open Usage and set the selected time window.
  2. Examine the drivers of cost, requests, or tokens.
  3. Review Budgets if the question is about cost-governance thresholds.

Use this journey for a shared view of AI spend for finance, operations, or engineering.

Next steps​