Skip to content

Operating pattern

Decide, refer, or stop

Give the pack a short list of permitted decisions and require referral when the evidence cannot support one.

Use when

A queue needs a permitted next state even when the record is incomplete or contradictory.

Operating contract

Authority, evidence, and stopping conditions.

Job to control
High-volume queues need a consistent next action, but the evidence is often incomplete, contradictory, or outside the operator’s authority.
Division of work
The pack gathers named evidence and chooses from permitted next steps. Missing evidence or an out-of-scope case becomes a stop or referral, not an improvised answer.
Control point
Fix the outcome vocabulary and referral criteria before review begins.
Evidence retained
Inputs consulted, missing or conflicting fields, rule applied, permitted outcome, and named next owner.
Human ownership
Own unresolved cases, policy exceptions, overrides, and any final action reserved to an accountable operator.
Trade-off
Narrow authority creates more referrals; that is the cost of keeping uncertain cases out of automated decisions.

Case sequence

  1. 01

    Receive the case

  2. 02

    Gather named evidence

  3. 03

    Apply the decision rules

  4. 04

    Decide or refer

  5. 05

    Record the decision and owner

Failure watch

Control intent and failure modes.

Control intent

Confident answers without evidence, silent guessing, and recommendations that cannot enter a controlled queue.

Failure modes

  • 01Treating missing data as negative evidence
  • 02Expanding the allowed outcomes in prose
  • 03Using escalation to avoid every difficult judgment

Applied in Cadre

Packs using this operating design.

Each pack narrows the pattern to a specific financial-services decision and names the seam that remains under human review.