Expected outcome
The queued task has a clear decision, rationale, confidence, and link back to its source evidence.
Tempera is in private preview and provides private APIs across its product areas. Access is arranged through onboarding for an agreed evaluation, with product-specific credentials, endpoints, and environment details supplied directly to your team. API maturity ranges from preview to research, and no shared cross-product endpoint is implied.
Before you start
- A provisioned review queue
- At least one trace or browser session routed for review
- A reviewer who understands the expected outcome
Steps
- 01
Open the highest-priority item
Start with the task and severity, then confirm why the agent requested review before opening deeper evidence.
- 02
Inspect only the relevant evidence
Read the source trace, browser action, or tool result needed for the decision. Keep redacted fields hidden unless the task explicitly requires approved access.
- 03
Record the outcome and reason
Approve, reject, or escalate the task and explain the deciding evidence in language another reviewer can follow.
- 04
Choose whether to reuse the case
Send recurring or important failures into the team's evaluation plan so a later agent version can be checked against the reviewed outcome.
What success looks like
- The decision is attached to its source evidence.
- The rationale and confidence are understandable to another reviewer.
- The team knows whether the case should become a reusable quality check.
If something is blocked
- If the task shows identifiers instead of useful context, ask the queue owner to improve the task presentation before continuing.
- If sensitive content appears unexpectedly, stop the review and ask the workspace owner to check the redaction boundary.
- If reviewers disagree, record the disagreement and settle the expected outcome before reusing the case.