Each page below is one decision point from the top-level map — one "play." The left pane recreates the FigJam tree exactly as drawn (same branch labels, same terminal boxes); the right pane is the same tree flattened into path → terminal state rows, so every route to an outcome can be checked line by line.

How I read each board: start at the entry decision, walk every arrow to a terminal box, and record the full condition path — then capture the sticky notes separately, because they answer a different question: not "what's the rule?" but "what do we do when the field is MISSING?" (look it up, assume a default, or follow up). Where two arrows overlap and the wiring is genuinely ambiguous, I did not guess — those became the questions at the bottom of the page.

Dashed-underlined terms open a ? glossary dialog — the shared vocabulary (UWing period, Knox Box, KYC, P(F), RCE…) captured while reading. Each page also notes where an agent helps: the exact spots a decision would stall on vague or missing info, and whether the unstick is a lookup, a derivation, the board's own assume-and-verify default, or one scoped question.