Discovery and the assurance profile

Discovery runs before any test. It answers one question: what can this environment prove?

dialogassert discover --target cards-support-prodlike

Connected successfully

Agent
cards-support-prodlike
LangGraph Agent Server

Evidence
Jaeger
service: cards-banking-agent
dialect: langsmith_otel

Correlation
✓ Automatically detected
langsmith.metadata.trace_id

Conversation coverage
✓ Multi-turn

Available verification
✓ Tool called
✓ Tool arguments
✓ Tool result
✓ Tool ordering
✓ Selected entity
✓ Answer grounding

Unavailable
— Human approval state
— Authoritative post-action state

Ready to test

The assurance profile

The output is a durable artefact, not just a connection check. It maps directly onto the evidence_required field of your control sets, so DialogAssert can tell you which controls are evaluable here before you spend a run finding out.

Cards Support Agent — Assurance Profile

Conversation evidence         ✓
Tool invocation               ✓
Tool arguments                ✓
Structured tool results       ✓
Turn attribution              ✓
Customer identity context     —
Approval state                —
External state verification   —

15 / 18 selected control types assertable
Overall evidence capability: GOOD
3 controls require additional evidence

Discovery supplies identifiers, never expectations

This boundary is deliberate and it is architectural.

Discovery may tell DialogAssert that:

"block card"  → tool currently named block_debit_card
card ID       → argument currently named card_id
success       → tool result currently exposes blocked=true

Only the approved control set may say:

Blocking requires confirmation.
Only the selected card may be blocked.
Successful blocking must actually change card state.

The system under test may teach DialogAssert how to observe it. It may never teach DialogAssert what “correct” means. Generated checks that use observed values absent from the business requirement are rejected rather than accepted.

Doctor

dialogassert doctor diagnoses an environment that is connected but not producing usable evidence — trace dialect detection, correlation strategy, turn coverage, decoded tool schema and which checks the environment can actually support.

dialogassert doctor --target cards-support-prodlike --explain selected-card-only

Related

• Connecting traces — trace sources and correlation.
• Inconclusive results — what happens when evidence is missing.