Branch Signal Evidence Triage

This workflow catches “confident wrong” decisions before they happen. When someone brings a branch metric, conversation summary, or attribution claim, the assistant first tries to answer using your Knowledge Base (definitions, metric specs, known caveats). If the request is more judgment-heavy, it routes the person into a short set of decision-shaped checklists.

The result is practical: the user leaves with a clear next step (what to verify, what to ignore, what to compare, and what usually breaks first) or gets handed off to an ops/analytics owner when the situation needs human judgment.

• Knowledge Base first, routing second: quick answers for known definitions and metric rules, with a clean escalation path.
• Decision-shaped menu covering trust, dirty signals, automation vs. judgment, branch comparisons, and signal culture.
• Built-in “polished noise” warnings: prompts users to validate provenance, timing, and incentives before believing a number.
• Fast handoff for high-stakes or ambiguous cases to an Analytics Ops department.

1. User Input starts the workflow when someone shares a question or claim about branch signals.
2. Knowledge Assistant attempts to answer from your Knowledge Base (and falls back to routing if the KB can’t confidently resolve it).
3. Pick what you’re deciding presents a button menu so the user can choose the type of decision risk they’re facing.
4. Based on the selection, the workflow sends one of the following playbooks:
   1. Which branch numbers deserve trust: a practical checklist for metric provenance, denominator games, and “too-clean” trendlines.
   2. Spot dirty signal before the meeting: fast tests for missingness, lag, selection bias, and narrative-first summaries.
   3. Automation vs. judgment: rules of thumb for when to trust automated scoring and when to force human review.
   4. Comparing branches & attribution: what teams routinely misread when branch contexts differ.
   5. Build a signal culture: lightweight operating habits that create decisions, not slide decks.
5. If the user picks Escalate to Analytics Ops, the workflow hands off with a clear message.

• No external credentials required.
• (Recommended) A maintained Calypso Knowledge Base covering: metric definitions, data sources by branch, known reporting lags, attribution rules, and standard caveats.
• (Optional) An internal handoff destination named Analytics Ops (or rename the department in the workflow).