Decision review

Watch the workflow: Import a bounded window and inspect coverage limits · Authored dummy data

Select the authored dummy decision source in Tensile, set a bounded UTC decision and stored-arrival window, and capture a pinned local report. No decision codes are recorded in this window. Inspect Source coverage: outcome rates stay held without customer policy attestation and independent evidence review; project coverage remains Unknown because the scan is finite. This demonstration reads only owned local dummy events, makes no external Braintrust call and records no policy attestation, source-code mapping or customer outcome.

Read the walkthrough transcript

• 00:00 — Select the dummy source and a bounded UTC window in Tensile.
• 00:05 — Capture the report. This bounded window contains no recorded decision codes.
• 00:11 — Outcome rates stay held without policy attestation and independent evidence review.
• 00:17 — Project coverage remains unknown. A finite scan cannot prove complete coverage.

Open Decision review to read findings about recorded decisions, grouped by outcome. A report is a pinned snapshot of one bounded source window. The review and the export read the same snapshot, so a reload or a shared link does not change the numbers.

Decision review is available only to enabled workspaces in production. If access is off, the page says Decision review is not enabled for this workspace. Ask your workspace administrator.

Before you start, connect a Braintrust project to the workspace and register it as a review source. See Braintrust.

Choose a source and a snapshotCopy Anchor Link

1. Open the Import tab.
2. Choose a connected source.
3. Import a bounded window to create a snapshot. Users who can configure the source can import.

Without a connected source, the page says No connected decision source and links to Settings.

Read the findingsCopy Anchor Link

The page has four tabs: Findings, Source coverage, Import and Reporting policy.

• Use the Account, Checklist item and date range controls to scope the report. The dates are UTC days, with both ends included.
• The outcome cards count findings by recorded outcome. Unresolved or withheld counts the rest.
• The findings list supports search, an outcome filter, sorting and paging.
• Select Download CSV to export every finding raised in the scope. The export ignores the search and outcome filters.

A finding takes its date from the start of the trace that raised it. A finding with no verified date does not appear in the list. The page counts it and links to Source coverage.

Check coverageCopy Anchor Link

Open Source coverage to see the date basis, the findings in range, the findings dated outside the range and the undated findings with the reason for each exclusion. It also shows the snapshot, the decision window and the stored-arrival scan. The project coverage is Unknown because the scan is finite.

Outcome rates show Held with the missing conditions. The conditions are a customer policy attestation, a policy that covers every account in view, findings in the view and an independent evidence review.

Record the reporting policyCopy Anchor Link

Open Reporting policy to record the policy for a source. Only users with the required customer-owner or administrator approval rights can record it. Without a saved source-code mapping, the tab says to save one in Import first.

Empty and failed statesCopy Anchor Link

• Choose a source, No source selected and No report snapshot selected tell you which step is missing.
• Snapshot unavailable means the link points to a snapshot that your workspace cannot open. Import a new window.
• An invalid date range shows an alert. It never widens to the whole snapshot.
• If a read fails, the page says so. It never shows a zero count instead.

Next stepsCopy Anchor Link

Review the traces behind a finding in User Stories.