Use cases - Armature

Use cases answers the product question behind the traffic: what are people actually trying to do? Armature’s models read every session, capture the user’s intent, and group semantically similar intents into named use cases.

The ranking

Each use case shows:

Column	Meaning
Volume	Sessions in this use case for the selected range.
Pass rate	How often those sessions succeed.
Share of traffic	This use case’s slice of all sessions.
Frustration	Low / medium / high, rolled up from per-session signals.

A use case with high volume and a low pass rate is usually the first thing to fix.

Unmet demand

Use cases are discovered from what users ask for, not from what your tools support, so demand you don’t serve yet still shows up, badged UNMET. For example, a “Bulk refunds” use case appears even when no refund tool exists. Agents can also report unmet needs directly: the SDK ships an optional request_capability tool whose calls land here.

Drilling in

Click a use case to see its sessions and stats; jump straight into session replay to watch real conversations from that use case. The Sessions page arrives pre-filtered.

How grouping works

Every session’s intent is embedded and matched against existing use cases; close matches join, the rest wait in an Others bucket.
When enough similar intents accumulate, they’re promoted into a new named use case automatically — no manual taxonomy to maintain.
On a brand-new workspace, the Overview panel is labeled provisional while the first clusters form; expect named use cases to stabilize as volume comes in.

⌘I