Branching Story Outline Workbench

How to use Branching Story Outline Workbench

Review the structure of your own branching reading activity before sharing it. The evidence shows a shortest entry route and a possible ending route for each passage, making disconnected sections and reachable traps visible. A separate script-free document links escaped passage text through generated local anchors.

1. Write original passage IDs, titles, plain text, ending flags and labeled target choices in the shown JSON shape.
2. Review broken choices, unreachable passages and reachable passages with no ending route in JSON evidence.
3. After correcting missing links, export the static HTML document and verify its reading and navigation flow in a browser.

Good to know

• At most 100 passages, 20 choices per passage, 300 total choices, 40,000 authored text characters and 100,000 input JSON characters. IDs and targets use exact case-sensitive strings. Duplicate IDs and a missing start are refused.
• Every passage declares ending as a boolean. Endings cannot have choices; ordinary passages without choices are reported as accidental dead ends. Missing targets remain visible in JSON and block HTML export.
• All choices are unconditional. A possible route to an ending does not mean every route terminates, especially when a reader repeatedly chooses a cycle. Shortest witnesses use breadth-first search with deterministic source-order ties.
• The JSON profile does not interpret Twine/Twee, story-format macros, variables, scripts, conditions, embedded media or HTML. The export contains escaped plain text, generated internal anchors and fixed CSS. It is a document prototype whose browser navigation, accessibility and print layout need native review before release.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.