Skip to main content
Two controlled dimensions make decisions comparable across agents and time: what the decision achieved (its outcome) and what kind of work it was (its intent).

​
Outcome

Every decision is classified into a single outcome class — the canonical description of its result. The outcome class is the primary group-by and filter dimension across the product, and it’s constrained at the database level to a fixed set of values. Alongside it, outcome_summary carries free-text colour — what the agent actually did — and decision_title is a short, scannable 3–5 word headline. The controlled values are:
Vocabulary note. Enfors standardized its outcome terminology across the whole product. The current canonical field is outcome_class (plus outcome_summary). The older final_verdict / verdict_label fields (PASS | REJECT | INCONCLUSIVE | PARTIAL) are deprecated and derived from outcome_class for backward compatibility only. New integrations should read outcome_class.

​
Decision intent (work type)

Each decision is also classified by intent — the type of work it represents — with a decision_intent_confidence score. Intent is what lets Enfors answer where the effort actually went: This classification, weighted by real decisions, powers the effort-mix breakdown in Pulse reports and the cost-per-work-type view in the Leader lens.
Effort-by-work-type breakdown

Effort breakdown by work type in a Pulse briefing

​
Why it matters

Because outcome and intent are structured (not free text), you can:
  • compare success rates across agents and people,
  • attribute cost to the kind of work that produced it,
  • and detect when an agent’s outcome mix drifts over time (Insights & Drift Detection).
Decisions captured before these fields existed carry NULL and surface as “unclassified.” Enfors backfills where possible.