Connections

Connections analyses your storyworld statically and shows which storylets can enable, disable, or otherwise influence which others - all from their conditions and outcomes alone. No playthroughs, no simulation. It's the fastest way to answer questions like "what turns this storylet on?", "what could turn it off?", and "if I delete this, what stops working?".

Connections runs entirely on your machine and changes nothing in the storyworld.

Where to find it

Connections is the fourth view tab on the Storylets page, next to Whiteboard, Cards, and Table. Click the Connections icon (four nodes joined by crossing lines) in the view switcher and the analysis runs automatically against whatever's in scope.

The scope follows wherever you are in the Storylets section:

• All Storylets - analyses the whole storyworld.
• A specific Deck - restricts to that deck's storylets.
• A specific Act - restricts to that act's storylets.

Switching between the Acts, Decks, and All Storylets containers keeps the Connections view in sync with whatever you drill into. Top-level Acts and Decks tabs (no specific container selected) show the whole-storyworld view.

Flipping between Whiteboard / Cards / Table / Connections is instant, and the analysis refreshes automatically once you edit a condition, an outcome, or a storylet's deck or act.

How it works

Connections walks every storylet's condition (to find what state it reads) and every outcome (to find what state it writes), then joins the two to produce edges between storylets. Each edge falls into one of three kinds drawn on the graph:

• Enable - The writer's outcome makes the reader's condition more likely to pass. Example: outcome sets @metMayor; another storylet gates on @metMayor.
• Disable - The writer makes the reader less likely to pass. Example: outcome clears a flag the reader requires.
• Influence - The writer touches state the reader cares about, but the polarity is not decidable statically. Example: outcome increments @x; reader compares @x == 3 - we know @x changes, but we cannot prove it will or will not equal 3.

Each kind has its own colour and line style, with a legend in the toolbar so Enable and Disable stay easy to tell apart at a glance.

There's a fourth kind of relationship the analyser tracks but does NOT draw on the graph:

• Shares reads with - Two storylets that read the same property's same value. They don't actually affect each other (both sit downstream of some other writer), so drawing edges between every pair of co-readers would misrepresent the signal. Instead, the inspector lists co-readers under Shares reads with as a navigation aid for "who else cares about this state?".

Focus mode

When you want to answer a question about one specific storylet - "why doesn't this fire?", "what would this break if I deleted it?", "what does its outcome affect?" - double-click any node on the graph to enter focus mode. The view narrows to that storylet plus the storylets it's connected to (one hop by default).

A Clear focus button appears in the toolbar; click it to go back to the full scope.

When you enter focus mode (or open the view fresh), Connections fits the visible graph into view for you. The Show All button refits it again any time.

Find Storylet

When a storylet is open in the right-hand editor pane, a crosshair Find Storylet button appears in the toolbar (before Show All). Click it and the graph pans to centre that storylet and selects its node - the right-rail swaps from the storylet editor to the connections inspector for that storylet, just as if you'd clicked the node on the graph.

The button only appears when the storylet is in the current scope (All Storylets always; a deck or act scope only when the storylet belongs to that container).

When you switch to the Connections view with a storylet already open in the editor (e.g. after navigating in via a deep-link), Find Storylet fires automatically so the context is right there.

Reading the graph

The graph is a node-link diagram. Storylets are boxes; edges between them carry the colour / style of their class. Acts are drawn as tinted boxes (each in its act's colour) so the phase structure of the storyworld stays visible at a glance.

• Click a node to open the inspector.
• Double-click to focus the analysis on it.

The inspector

Clicking a node on the graph opens the right-rail inspector (the same rail the storylet editor uses). It shows:

• The storylet's title, with a colour wash matching its deck.
• An Edit button that closes the Connections inspector and opens the storylet editor in the same rail.
• This storylet affects - everything its outcomes can enable, disable, or influence.
• Is affected by - the reverse direction; everything that can enable / disable / influence this storylet's condition.
• Shares reads with - co-readers; storylets that gate on the same property value as this one. Useful for "who else cares about this state?" without implying a cause-and-effect relationship.

Each entry has a via column listing the properties (or the specific flags) that link the two storylets.

Click any storylet name in the inspector to re-focus the graph on it.

What Connections does not do

• It doesn't replace Coverage Testing. Coverage tells you what storylets were exercised over many random playthroughs. Connections tells you what storylets could affect each other from the data alone. The two answer different questions.
• It doesn't follow play-history dependencies. Conditions that test count_played_tag() or turns_since_tag() depend on which storylets have actually been played, not on any other storylet's outcomes, so they're skipped.
• It doesn't simulate. When an outcome's new value is computed rather than a fixed value, Connections reports the link as Influence rather than a definite enable or disable. That's deliberately cautious: the alternative would be drawing edges that are sometimes wrong.

When to use it

• Adding a new storylet - after wiring it up, double-click to focus and check it's connected the way you expected (it enables the right downstream beats, gates correctly on the right upstream outcomes).
• Debugging dead content - if Coverage shows a storylet never fires, open it in the Storylets editor, switch to the Connections view, and double-click the node to see whether anything in scope can enable its condition at all.
• Refactoring - before deleting an outcome or storylet, focus on it to see what downstream beats it currently enables / disables, so you know what has to be re-wired.
• Reading someone else's storyworld - the Connections view at All Storylets scope is the fastest way to get a feel for how an act's beats hang together.