Clusy guide: Keep the branch you didn’t choose so the conclusion can be checked
Use one shared worksheet and two fictional notebook branches to check whether a count can be reconstructed and the rejected alternative is explained.
Keeping only the winning branch can be enough to present a conclusion, but not to explain why another option was rejected. In its June 2026 launch notes, Clusy described experiment branches from a common notebook node, where results can be compared together and unselected branches kept for review. The point is not seeing two columns at once; it is knowing whether both used the same starting material and counting rule.
Check one conclusion across three sheets of paper
The starting sheet has five shapes: filled circle, outline circle, filled triangle, filled circle, outline triangle. Count circles, both filled and outline. Branch A says 3 and marks shapes 1, 2, and 4; B says 2 and marks only 1 and 4. Both start from the same sheet. Explain that B missed the second shape, an outline circle, rather than claiming A was faster or B was equally valid.
Now change B’s rule to “count only filled circles” and leave its result at 2. That number answers B’s own question but cannot be ranked against A under the original goal. “A=3, B=2” alone cannot distinguish a missed item from a changed rule. Ask another reader to identify the shared starting point, the rule that differs, and which result answers the original question using just the three sheets. If any of the three is missing, the results table is not a complete handoff.
When a branching tool is unnecessary
Clusy is worth considering if colleagues need to review several alternatives and keeping notebook branches is part of the handoff. For a simple comparison that won’t change, a static table naming the worksheet, rule, and judgments is enough. This is a paper exercise; nothing was run or shared in the software. It does not verify that exports retain branch relationships. If the handoff requires a single offline file, the branch view alone does not meet that requirement.
Content note:This article is based on publicly available information and is intended as a reference for evaluating tools. Features, pricing, and related policies may change at any time; please refer to the latest official information.
Original source:www.clusy.io