# Separate workflow path coverage from outcome coverage

Illustrative planning brief; no automatic product import.

Synthetic planning case: A toy model has two distinct routes ending accepted: pending→ready→accepted and pending→amended→accepted. It also permits pending→cancelled. The first two routes pass rehearsal.

## Decision

Two passing paths cover one of the two declared terminal outcomes. Accepted has evidence; cancelled has none. Retain both path diversity and terminal-outcome coverage as separate counts.

## Owned work

- Declare terminal outcomes
  - Owner role: Model owner
  - Acceptance evidence: Accepted and cancelled have no outgoing edges in this toy model.
- Map paths to actual terminals
  - Owner role: Reviewer
  - Acceptance evidence: Both recorded traces end accepted through different intermediates.
- Exercise the missing outcome
  - Owner role: Rehearsal owner
  - Acceptance evidence: Cancellation has its own expected terminal state and receiving evidence.

## Workflow

1. Declare terminal outcomes. Check: Accepted and cancelled have no outgoing edges in this toy model.
2. Map paths to actual terminals. Check: Both recorded traces end accepted through different intermediates.
3. Exercise the missing outcome. Check: Cancellation has its own expected terminal state and receiving evidence.

## Judgment

The enumerated routes are invented and bounded; they do not describe every possible real task history.


## Filled manual planning note

Two passing paths cover one of the two declared terminal outcomes. Accepted has evidence; cancelled has none. Retain both path diversity and terminal-outcome coverage as separate counts. There are three declared routes and two terminal outcomes. Two rehearsed routes give 2/3 route coverage but only 1/2 terminal-outcome coverage, because both end accepted. The enumerated routes are invented and bounded; they do not describe every possible real task history.


## Working artifact

- Route coverage / Two of three declared routes / Preserve path-specific evidence
- Outcome coverage / Accepted only, one of two terminals / Do not double-count accepted
- Cancellation outcome / No observed trace / Assign bounded receiving check


## Workflow questions

### Is the second accepted path redundant?

Not necessarily. It supplies a different route even though it adds no new terminal outcome.

### Does every outcome imply every route worked?

No. Route coverage and outcome coverage describe different obligations.

## Product connection

Use the owned checks and downloaded brief to discuss this planning decision alongside your TeamBoostAI tasks. Confirm available fields, roles and account features separately. The example is manual; it does not calculate live analytics, create work or run an experiment in the product.

Confirm account availability before adopting this manual outline.

## Original worked case

Synthetic records, manual planning only. No account import or live analytics.

### Inspect the invented case records

Declared route | Terminal outcome | Rehearsal
--- | --- | ---
Pending → ready → accepted | Accepted | Pass
Pending → amended → accepted | Accepted | Pass
Pending → cancelled | Cancelled | None

### Reasoning

There are three declared routes and two terminal outcomes. Two rehearsed routes give 2/3 route coverage but only 1/2 terminal-outcome coverage, because both end accepted.

### Bounded result

Two passing paths cover one of the two declared terminal outcomes. Accepted has evidence; cancelled has none. Retain both path diversity and terminal-outcome coverage as separate counts.

### Distinct decision

The worked case separates distinct path count from terminal-outcome coverage on the same declared graph.

### Limits

The enumerated routes are invented and bounded; they do not describe every possible real task history.

### Definitions and method context

- NIST: state-based and event-sequence testing context — https://csrc.nist.gov/Projects/automated-combinatorial-testing-for-software — General context for state-based and event-sequence testing. All graphs, guards, fixtures and recovery contracts here are original toy definitions; the source does not certify their completeness or product behavior.