Branch Signal Sensemaking Guide

This workflow turns “we have a lot of signals” into “we can safely make a call.” It greets an inbound question, uses your Knowledge Base to answer what it can, then routes the person into a set of decision-shaped playbooks that catch the most common ways branch numbers look credible right up until the meeting gets expensive.

Operators use it as a lightweight decision coach inside Calypso: users pick the situation they’re in (trusting branch numbers, spotting dirty signal, comparing branches, etc.) and get a practical checklist that favors judgment over jargon.

• Knowledge Base first, then structured routing (so repeat questions get answered fast)
• Button-based menu for common decision scenarios (branch metrics, attribution, signal hygiene)
• “Reality check” guidance designed to surface dirty signal before leaders commit
• Clear guidance on where automation is reliable vs where human judgment must stay in the loop
• Optional handoff path to a human owner when the situation is high-stakes or ambiguous

1. User Input starts when someone asks for help making sense of branch signals.
2. Knowledge Assistant attempts to answer using your Knowledge Base, and falls back to routing when the question is messy, novel, or decision-specific.
3. Pick what you’re deciding presents a menu of decision scenarios.
4. Based on the button selected, the workflow sends a focused playbook:
   1. Which branch numbers deserve trust? → practical trust tests and “polished noise” traps.
   2. Spot dirty signal before the meeting → fast diagnostics for broken definitions, selection bias, and logging gaps.
   3. Automation vs human judgment → rules of thumb for what to automate and what to keep reviewable.
   4. Messy evidence → usable insight → how to reduce chaos without cleaning away the truth.
   5. Comparing branches & attribution → common misreads and how to compare fairly.
   6. Build a signal culture (not a slide culture) → operating habits that produce decisions, not decks.
   7. Talk to a human → routes to a human owner for high-stakes calls.

• Calypso Inbox enabled for user messaging.
• (Recommended) A populated Calypso Knowledge Base with your metric definitions, branch event taxonomy, attribution rules, and “source of truth” owners.
• No external credentials are required for this workflow as written.