QEDQED
App GuideMain LayoutThreads

Threads

Promises and questions your story opens - and whether they're paid off.

Threads

AI-assisted - threads are inferred by the analysis agent from your dialogue, so this rail needs a connected model and a run. It's the agent's reading, not authored truth.

A thread is a promise or question the story opens and (maybe) pays off - a mystery, a goal, a conflict. Its status is a fold over its events: a resolve closes it, a later reopen re-opens it. A thread can fork into strands (per subject) - e.g. one layoff thread, one strand per person.

Threads is the home of a tabbed rail; its siblings - Character Arcs, Entities, and Lore - share the tab strip.

The thread map for Romance of the Three Kingdoms: every promise the story makes, and where it pays off.

The thread map for Romance of the Three Kingdoms: every promise the story makes, and where it pays off.

Reading the map

lane colorthe archetype (mystery · promise · conflict · task · foreshadowing)
lane opacitysolid = open · faded = resolved
● openthe event that opened the thread
• advancean event that develops it
◆ resolvean event that closes it (the gate is met)
◌ reopena later event that re-opens a closed thread
columnsscenes in reading order - click one to read it
chapter bandsthe wrap-layer groups scenes by folder; toggle with the layers button

The sheet (click a thread)

A chapter railway: each chapter is a station - a filled stop (●) where the thread has events, a hollow stop (○ ··) for a chapter it stays quiet, a ◆ terminus where it resolves. Events are cards under their station; click one to expand its full moment, the evidence dialogue it was drawn from, the surrounding scene context, and its cast. The hollow stops show how long a thread goes silent - a slow burn, or a thread left hanging.

Copyright © 2025-2026, QED by Nelworks

On this page