Journeys
Learn how a customer task becomes a versioned test plan with success, safety, recovery, and coverage checks.
A journey is one customer task that an AI agent should complete in your product. It defines the intended result, protected behavior, recovery expectations, and the evidence required for a trustworthy decision.
Example
A customer asks to move from the Starter plan to the Growth plan.
Confirm the new plan and billing date. Do not create a second subscription.Invokeable turns this description into a reviewable plan. You can edit the plan before it is used.
Journey definition
A useful journey includes:
- A name and intent written in customer language
- Starting conditions and the acting customer's permissions
- Required and optional product actions
- The correct final product state
- Results that are required for success
- Forbidden actions and states
- Confirmation expectations
- Recovery expectations
- Completion criteria and failure severity
Test cases and coverage
A journey can have several test cases. Test cases cover normal execution, input variation, missing information, product failures, uncertain results, delayed state changes, cancellation, and recovery.
Coverage shows whether the required situations have approved test cases. More test cases are not automatically better. Each case should represent a meaningful condition and a result that Invokeable can verify.
Lifecycle
- Draft journeys can be edited but are not ready to run.
- In review journeys await approval.
- Approved journeys can run when their actions and agents are ready.
- Superseded or withdrawn versions remain linked to historical runs.
Keep one customer goal per journey
Split unrelated tasks into separate journeys. Narrow journeys produce clearer evidence and findings.
See Create a journey and Run an assessment.