Skip to content
Docs

Business journeys

A business journey is the human-authored description of what the customer says and what the agent must satisfy.

The MVP business-owned file contains only:

  • turns
  • acceptance
turns:
  - I would like to block my card.
  - the card ending with {card_number}.
  - yes, please go ahead


acceptance:
  - Agent shows the customer their cards before asking which card to block.
  - Agent blocks only the card selected by the customer.
  - Agent asks for confirmation before blocking.
  - Agent confirms the card is blocked only after the action succeeds.

No tool catalogue. No fixture schema. No trajectory DSL. Runtime values stay in a separate inputs file, and engineering can add trajectory checks where deeper implementation assurance is useful.

Section titled “Recommended authoring pattern”

Business users should write:

turns:
  - Customer asks a realistic question.
  - Customer provides any required selection or confirmation.


acceptance:
  - Agent obligation one.
  - Agent obligation two.
  - Agent forbidden behavior.

Engineering should provide the agent config, runtime inputs, and optionally trajectory tests, domain packs and deterministic assertion packs. DialogAssert generates the workflow capture, acceptance rubric, hidden run config and both reports.