Skip to main content
tempera

No product access needed

Understand an example browser session

Use one illustrative refund workflow to identify the separate Tempo session, human decision, Palette trace, and onboarding-configured reference. Correlation is not automatic.

Expected outcome

You can explain what Tempo, a human decision, and Palette each verify, and why an explicit correlation must be configured before records are treated as one evaluation case.

You can use this public guide without a Tempera account, product credential, or private workspace. Product access begins only after private onboarding.

Before you start

  • A browser-agent workflow you want to make more reliable

Steps

  1. 01

    Start with a bounded job

    A support agent opens an approved customer-operations site to review a refund request. The example is illustrative, not a customer result or production benchmark.

  2. 02

    Inspect the Tempo session

    Tempo records the context needed to inspect the browser actions. It can hold an exact consequential action for explicit human confirmation. This verifies the Tempo session and action boundary; it does not prove that a Palette trace exists.

  3. 03

    Review the exact decision

    A provisioned review step can present the relevant action, source evidence, proposed outcome, and reason review was requested. The reviewer can approve, reject, or escalate that action without implying that the decision has already been attached to a Palette trace.

  4. 04

    Verify the Palette record separately

    Palette can store a review annotation on a trace and use that trace as a candidate evaluation case. When an evaluation also uses a Tempo session, private onboarding defines and checks the explicit reference between the two records. Palette does not infer that relationship; correlation is not automatic.

What success looks like

  • A Tempo session record shows what the browser agent did.
  • A reviewer can record a decision about the exact consequential action.
  • A Palette trace can carry its own review annotation and inform a later evaluation.
  • Any relationship between the Tempo session and Palette trace uses the explicit correlation configured and checked during private onboarding.

If something is blocked

  • If session, trace, review, and evaluation still sound interchangeable, name the Tempo record, human decision, Palette record, and configured correlation separately.
  • If your workflow has no sensitive decision, choose a failure you already investigate after release and use that as the evaluation case.