# Glossary (/docs/reference/glossary)



## A [#a]

**Action**: One product operation an agent can use, including its inputs, access, risk, confirmation, retry, recovery, and verification behavior.

**Agent environment**: A connected agent, its supported capabilities, operating limits, compatibility result, and lifecycle state.

**Assessment**: The planned evaluation of a journey and its test cases against one or more agent environments.

## B [#b]

**Baseline**: An approved reference for expected journey behavior used in later comparisons.

## C [#c]

**Catalog**: The workspace inventory of product surfaces and actions available for review and assessment use.

**Check**: One evidence-backed evaluation of behavior such as action selection, input validity, final state, safety, recovery, or communication.

**Cleanup**: Work that restores or removes temporary state created by an assessment.

**Coverage**: The approved test cases and variations that exercise required journey conditions.

## E [#e]

**Evidence**: The authorized record of actions, observations, product state, verification, cleanup, and limitations used to support a decision.

## F [#f]

**Finding**: A reliability or safety problem supported by one or more assessment results.

## J [#j]

**Journey**: One customer task, its intended result, protected behavior, recovery expectations, and verification criteria.

## P [#p]

**Product connection**: The MCP or OpenAPI endpoint and environment details used to discover and call product actions.

**Product surface**: A customer-facing product area that groups related actions.

## R [#r]

**Readiness**: The workspace decision based on verified outcomes, unresolved blockers, required coverage, and evidence freshness.

**Run**: One execution record within an assessment.

## S [#s]

**Safety limit**: A time, action, spend, confirmation, authorization, or behavior boundary applied to assessment execution.

**Scenario**: A test case that applies the journey to a meaningful normal, edge, failure, uncertainty, or recovery condition.

**Side effect**: A product change caused by an action, such as creating, updating, sending, charging, deleting, or canceling something.

## V [#v]

**Verification**: An independent check of the product state after an action or run.

**Variation**: A planned change to inputs, conditions, environment, or recovery path within journey coverage.

**Version**: An immutable revision of a journey, action, policy, test group, baseline, or other decision-relevant definition.

## W [#w]

**Workspace**: One organization's Invokeable data and access boundary.