WO-47e visible branch/condition proof

Different answers should select different result tiers and routes.

This page uses the real SDK with a preview schema. It does not create leads, but it evaluates the same branch-rule shape agents author: bare answer ids, `answers.` fields, score fallback, result tiers, and route ids.

What this proves

Schemaflow.branch_rules + flow.result_tiers + routes

High pathbudget = enterprise and timeline in this_quarter selects tier_high and route_book.

Low pathanswers.budget = starter selects tier_low and route_overview.

FallbackIf no branch rule matches, score thresholds select tier_mid and route_resource.

SafetypreviewSchema skips attempt/event writes, so this page is safe for Demo/SSOT and agent authoring.

Enterprise fast track Branch rule: bare answer id + `in` operator. Result: Talk to sales, route_book.

Starter nurture Branch rule: `answers.` field compatibility. Result: Overview, route_overview.

Score fallback No branch rule matches. Score threshold picks the mid tier and route_resource.

Current target: tier_high / route_book

Click path: Enterprise budget, this quarter timeline

Different answers should select different result tiers and routes.

Interactive SDK preview