A four-state word tree that branches raw phrases out from a root term — ribbon width is that continuation's share, every word is a focusable button that re-roots the tree, and the breadcrumb walks back.
Preview in your theme
Loading preview…
This component is part of Pro
The install command, prompt and concept map are included with a Pro license — one purchase unlocks every Pro component, forever.
status="ready" · direction="suffix" — 639 mentions of “we need” across 27 of the 30 notes. Twelve distinct next words: with maxChildren=8 the seven heaviest get a word each and the remaining five collect into one dashed “+5 rarer” bucket, which carries their 25 mentions and is the only mark that can’t be re-rooted. “to” alone takes 328 of the 639, 51.3%, which is why its trunk is half the stack. Click a word — or press Enter on it — to re-root there. Last root reported by onRootChange: none yet.
Retro notes · what follows “we need”30 retro notes · counts are mentions, not notes
639 mentions · 8 of 12 continuations drawn · 23 rows · 4 words deep
1 folded · 25 behind them
Word tree for we need: 639 mentions across 27 phrases, continuing into 12 distinct next words, of which 8 are drawn to the right over 23 rows and 4 words deep. Heaviest continuation to, 328 mentions, 51.3%. 1 word is still folded, holding 25 mentions. 3 phrases do not contain the term at all. Every drawn continuation is listed in the table that follows.
we need639
Ribbon thickness is that continuation’s share of we need, on one scale for the whole picture; the exact figure is printed beside every word. Branches leaving a fork stack across the trunk they come out of, so the unused part of a trunk is the phrases that stop there. Click a word — or press Enter on it — to make it the new root; the path above walks back.
481 mentions carry on past the 4-word depth this tree follows. Raise maxDepth to keep going, or re-root further along to pick the phrase back up.
3 of 30 phrases never say we need, so they are not drawn. Occurrences are counted per mention: a phrase saying it twice contributes two branches.
Every continuation currently drawn from we need, with how many occurrences take it, its share of the root, how many phrases stop there and what is still folded behind it.
Continuation
Word
mentions
Share
Stops here
Folded behind it
State
we need to
1 of 4
328
51.3%
—
—
open
we need a
1 of 4
87
13.6%
—
—
open
we need more
1 of 4
82
12.8%
—
—
open
we need better
1 of 4
70
11%
—
—
open
we need your
1 of 4
30
4.7%
—
—
open
we need this
1 of 4
9
1.4%
9
—
end of the phrase
we need clarity
1 of 4
8
1.3%
—
—
open
+5 rarer, under we need
1 of 4
25
3.9%
—
5 continuations, 25
grouped, not re-rootable
we need to fix
2 of 4
138
21.6%
—
—
open
we need to ship
2 of 4
95
14.9%
—
—
open
we need to talk
2 of 4
51
8%
—
—
open
we need to hire
2 of 4
26
4.1%
—
—
open
we need to write
2 of 4
18
2.8%
—
—
open
we need to fix the
3 of 4
138
21.6%
—
—
open
we need to fix the flaky
4 of 4
64
10%
64
—
end of the phrase
we need to fix the onboarding
4 of 4
41
6.4%
41
—
end of the phrase
we need to fix the billing
4 of 4
33
5.2%
33
—
end of the phrase
we need to ship the
3 of 4
95
14.9%
—
—
open
we need to ship the export
4 of 4
58
9.1%
58
—
end of the phrase
we need to ship the mobile
4 of 4
37
5.8%
37
—
end of the phrase
we need a proper
2 of 4
44
6.9%
—
—
open
we need a second
2 of 4
31
4.9%
—
—
open
we need a shared
2 of 4
12
1.9%
—
—
open
we need more time
2 of 4
39
6.1%
—
—
open
we need more examples
2 of 4
27
4.2%
—
—
open
we need more headcount
2 of 4
16
2.5%
—
—
open
we need better error
2 of 4
35
5.5%
—
—
open
we need better dashboards
2 of 4
21
3.3%
—
—
open
we need better docs
2 of 4
14
2.2%
14
—
end of the phrase
we need to talk about
3 of 4
51
8%
—
—
open
we need to talk about pricing
4 of 4
29
4.5%
29
—
end of the phrase
we need to talk about the
4 of 4
22
3.4%
22
—
end of the phrase
we need a proper status
3 of 4
44
6.9%
—
—
open
we need a proper status page
4 of 4
44
6.9%
44
—
end of the phrase
we need more time to
3 of 4
39
6.1%
—
—
open
we need more time to test
4 of 4
39
6.1%
39
—
end of the phrase
we need better error messages
3 of 4
35
5.5%
—
—
open
we need better error messages in
4 of 4
35
5.5%
35
—
end of the phrase
we need a second on-call
3 of 4
31
4.9%
—
—
open
we need a second on-call rotation
4 of 4
31
4.9%
31
—
end of the phrase
we need your approval
2 of 4
19
3%
—
—
open
we need your team
2 of 4
11
1.7%
—
—
open
we need more examples in
3 of 4
27
4.2%
—
—
open
we need more examples in the
4 of 4
27
4.2%
27
—
end of the phrase
we need to hire another
3 of 4
26
4.1%
—
—
open
we need to hire another reviewer
4 of 4
26
4.1%
26
—
end of the phrase
we need better dashboards for
3 of 4
21
3.3%
—
—
open
we need better dashboards for the
4 of 4
21
3.3%
21
—
end of the phrase
we need your approval on
3 of 4
19
3%
—
—
open
we need your approval on the
4 of 4
19
3%
19
—
end of the phrase
we need to write the
3 of 4
18
2.8%
—
—
open
we need to write the migration
4 of 4
18
2.8%
18
—
end of the phrase
we need more headcount on
3 of 4
16
2.5%
—
—
open
we need more headcount on support
4 of 4
16
2.5%
16
—
end of the phrase
we need a shared glossary
3 of 4
12
1.9%
—
—
open
we need a shared glossary for
4 of 4
12
1.9%
12
—
end of the phrase
we need your team to
3 of 4
11
1.7%
—
—
open
we need your team to review
4 of 4
11
1.7%
11
—
end of the phrase
we need clarity on
2 of 4
8
1.3%
—
—
open
we need clarity on the
3 of 4
8
1.3%
—
—
open
we need clarity on the deprecation
4 of 4
8
1.3%
8
—
end of the phrase
direction="prefix" — the other half of every sentence, and a different question: what leads up to “we need”. Six openers, no bucket needed, and 59 of the 639 mentions stop dead at the root because the note opens with the term. Arrow keys mirror with the drawing: left steps into the heaviest word before this one, right walks back toward the root.
Retro notes · what follows “we need”What comes before it
639 mentions · 6 of 6 continuations drawn · 6 rows · 4 words deep
Word tree for we need: 639 mentions across 27 phrases, continuing into 6 distinct next words, of which 6 are drawn to the left over 6 rows and 4 words deep. Heaviest continuation honestly, 154 mentions, 24.1%. 59 start with it. 3 phrases do not contain the term at all. Every drawn continuation is listed in the table that follows.
we need639
Ribbon thickness is that continuation’s share of we need, on one scale for the whole picture; the exact figure is printed beside every word. Branches leaving a fork stack across the trunk they come out of, so the unused part of a trunk is the phrases that stop there. Click a word — or press Enter on it — to make it the new root; the path above walks back.
3 of 30 phrases never say we need, so they are not drawn. Occurrences are counted per mention: a phrase saying it twice contributes two branches.
Every continuation currently drawn from we need, with how many occurrences take it, its share of the root, how many phrases stop there and what is still folded behind it.
Continuation
Word
mentions
Share
Stops here
Folded behind it
State
honestly we need
1 of 4
154
24.1%
154
—
end of the phrase
think we need
1 of 4
117
18.3%
—
—
open
realistically we need
1 of 4
97
15.2%
97
—
end of the phrase
retro we need
1 of 4
89
13.9%
—
—
open
point we need
1 of 4
66
10.3%
—
—
open
sprint we need
1 of 4
57
8.9%
—
—
open
I think we need
2 of 4
117
18.3%
117
—
end of the phrase
the retro we need
2 of 4
89
13.9%
—
—
open
in the retro we need
3 of 4
89
13.9%
89
—
end of the phrase
some point we need
2 of 4
66
10.3%
—
—
open
at some point we need
3 of 4
66
10.3%
66
—
end of the phrase
next sprint we need
2 of 4
57
8.9%
—
—
open
the next sprint we need
3 of 4
57
8.9%
—
—
open
before the next sprint we need
4 of 4
57
8.9%
57
—
end of the phrase
Row-per-mention feed — the same 639 mentions arriving as 665 individual rows with no count field, shuffled with a fixed seed. Identical tree: count is a convenience for pre-aggregated feeds, not a second code path, and array order never touches the layout because ties are broken on the word itself.
Retro notes · row-per-mention feedOne row per mention, shuffled · the same tree, built from 665 rows
639 mentions · 8 of 12 continuations drawn · 23 rows · 4 words deep
1 folded · 25 behind them
Word tree for we need: 639 mentions across 639 phrases, continuing into 12 distinct next words, of which 8 are drawn to the right over 23 rows and 4 words deep. Heaviest continuation to, 328 mentions, 51.3%. 1 word is still folded, holding 25 mentions. 26 phrases do not contain the term at all. Every drawn continuation is listed in the table that follows.
we need639
Ribbon thickness is that continuation’s share of we need, on one scale for the whole picture; the exact figure is printed beside every word. Branches leaving a fork stack across the trunk they come out of, so the unused part of a trunk is the phrases that stop there. Click a word — or press Enter on it — to make it the new root; the path above walks back.
481 mentions carry on past the 4-word depth this tree follows. Raise maxDepth to keep going, or re-root further along to pick the phrase back up.
26 of 665 phrases never say we need, so they are not drawn. Occurrences are counted per mention: a phrase saying it twice contributes two branches.
Every continuation currently drawn from we need, with how many occurrences take it, its share of the root, how many phrases stop there and what is still folded behind it.
Continuation
Word
mentions
Share
Stops here
Folded behind it
State
we need to
1 of 4
328
51.3%
—
—
open
we need a
1 of 4
87
13.6%
—
—
open
we need more
1 of 4
82
12.8%
—
—
open
we need better
1 of 4
70
11%
—
—
open
we need your
1 of 4
30
4.7%
—
—
open
we need this
1 of 4
9
1.4%
9
—
end of the phrase
we need clarity
1 of 4
8
1.3%
—
—
open
+5 rarer, under we need
1 of 4
25
3.9%
—
5 continuations, 25
grouped, not re-rootable
we need to fix
2 of 4
138
21.6%
—
—
open
we need to ship
2 of 4
95
14.9%
—
—
open
we need to talk
2 of 4
51
8%
—
—
open
we need to hire
2 of 4
26
4.1%
—
—
open
we need to write
2 of 4
18
2.8%
—
—
open
we need to fix the
3 of 4
138
21.6%
—
—
open
we need to fix the flaky
4 of 4
64
10%
64
—
end of the phrase
we need to fix the onboarding
4 of 4
41
6.4%
41
—
end of the phrase
we need to fix the billing
4 of 4
33
5.2%
33
—
end of the phrase
we need to ship the
3 of 4
95
14.9%
—
—
open
we need to ship the export
4 of 4
58
9.1%
58
—
end of the phrase
we need to ship the mobile
4 of 4
37
5.8%
37
—
end of the phrase
we need a proper
2 of 4
44
6.9%
—
—
open
we need a second
2 of 4
31
4.9%
—
—
open
we need a shared
2 of 4
12
1.9%
—
—
open
we need more time
2 of 4
39
6.1%
—
—
open
we need more examples
2 of 4
27
4.2%
—
—
open
we need more headcount
2 of 4
16
2.5%
—
—
open
we need better error
2 of 4
35
5.5%
—
—
open
we need better dashboards
2 of 4
21
3.3%
—
—
open
we need better docs
2 of 4
14
2.2%
14
—
end of the phrase
we need to talk about
3 of 4
51
8%
—
—
open
we need to talk about pricing
4 of 4
29
4.5%
29
—
end of the phrase
we need to talk about the
4 of 4
22
3.4%
22
—
end of the phrase
we need a proper status
3 of 4
44
6.9%
—
—
open
we need a proper status page
4 of 4
44
6.9%
44
—
end of the phrase
we need more time to
3 of 4
39
6.1%
—
—
open
we need more time to test
4 of 4
39
6.1%
39
—
end of the phrase
we need better error messages
3 of 4
35
5.5%
—
—
open
we need better error messages in
4 of 4
35
5.5%
35
—
end of the phrase
we need a second on-call
3 of 4
31
4.9%
—
—
open
we need a second on-call rotation
4 of 4
31
4.9%
31
—
end of the phrase
we need your approval
2 of 4
19
3%
—
—
open
we need your team
2 of 4
11
1.7%
—
—
open
we need more examples in
3 of 4
27
4.2%
—
—
open
we need more examples in the
4 of 4
27
4.2%
27
—
end of the phrase
we need to hire another
3 of 4
26
4.1%
—
—
open
we need to hire another reviewer
4 of 4
26
4.1%
26
—
end of the phrase
we need better dashboards for
3 of 4
21
3.3%
—
—
open
we need better dashboards for the
4 of 4
21
3.3%
21
—
end of the phrase
we need your approval on
3 of 4
19
3%
—
—
open
we need your approval on the
4 of 4
19
3%
19
—
end of the phrase
we need to write the
3 of 4
18
2.8%
—
—
open
we need to write the migration
4 of 4
18
2.8%
18
—
end of the phrase
we need more headcount on
3 of 4
16
2.5%
—
—
open
we need more headcount on support
4 of 4
16
2.5%
16
—
end of the phrase
we need a shared glossary
3 of 4
12
1.9%
—
—
open
we need a shared glossary for
4 of 4
12
1.9%
12
—
end of the phrase
we need your team to
3 of 4
11
1.7%
—
—
open
we need your team to review
4 of 4
11
1.7%
11
—
end of the phrase
we need clarity on
2 of 4
8
1.3%
—
—
open
we need clarity on the
3 of 4
8
1.3%
—
—
open
we need clarity on the deprecation
4 of 4
8
1.3%
8
—
end of the phrase
maxChildren={4} · maxDepth={3} · maxRows={14} — the same corpus read narrowly. Three words and a dashed “+9 rarer” bucket carrying 142 mentions at the first fork, three words of continuation followed instead of four, and 186 mentions held inside the two dashed buckets. A rendering budget, never a filter: the figures on the card still count all 639, and every folded word is one Enter away.
Retro notes · what follows “we need”Narrow read · everything folded is one Enter away
639 mentions · 4 of 12 continuations drawn · 11 rows · 3 words deep
2 folded · 186 behind them
Word tree for we need: 639 mentions across 27 phrases, continuing into 12 distinct next words, of which 4 are drawn to the right over 11 rows and 3 words deep. Heaviest continuation to, 328 mentions, 51.3%. 2 words are still folded, holding 186 mentions. 3 phrases do not contain the term at all. Every drawn continuation is listed in the table that follows.
we need639
Ribbon thickness is that continuation’s share of we need, on one scale for the whole picture; the exact figure is printed beside every word. Branches leaving a fork stack across the trunk they come out of, so the unused part of a trunk is the phrases that stop there. Click a word — or press Enter on it — to make it the new root; the path above walks back.
603 mentions carry on past the 3-word depth this tree follows. Raise maxDepth to keep going, or re-root further along to pick the phrase back up.
3 of 30 phrases never say we need, so they are not drawn. Occurrences are counted per mention: a phrase saying it twice contributes two branches.
Every continuation currently drawn from we need, with how many occurrences take it, its share of the root, how many phrases stop there and what is still folded behind it.
Continuation
Word
mentions
Share
Stops here
Folded behind it
State
we need to
1 of 3
328
51.3%
—
—
open
we need a
1 of 3
87
13.6%
—
—
open
we need more
1 of 3
82
12.8%
—
—
open
+9 rarer, under we need
1 of 3
142
22.2%
—
9 continuations, 142
grouped, not re-rootable
we need to fix
2 of 3
138
21.6%
—
—
open
we need to ship
2 of 3
95
14.9%
—
—
open
we need to talk
2 of 3
51
8%
—
—
open
+2 rarer, under we need to
2 of 3
44
6.9%
—
2 continuations, 44
grouped, not re-rootable
we need to fix the
3 of 3
138
21.6%
138
—
end of the phrase
we need to ship the
3 of 3
95
14.9%
95
—
end of the phrase
we need a proper
2 of 3
44
6.9%
—
—
open
we need a second
2 of 3
31
4.9%
—
—
open
we need a shared
2 of 3
12
1.9%
—
—
open
we need more time
2 of 3
39
6.1%
—
—
open
we need more examples
2 of 3
27
4.2%
—
—
open
we need more headcount
2 of 3
16
2.5%
—
—
open
we need to talk about
3 of 3
51
8%
51
—
end of the phrase
we need a proper status
3 of 3
44
6.9%
44
—
end of the phrase
we need more time to
3 of 3
39
6.1%
39
—
end of the phrase
we need a second on-call
3 of 3
31
4.9%
31
—
end of the phrase
we need more examples in
3 of 3
27
4.2%
27
—
end of the phrase
we need more headcount on
3 of 3
16
2.5%
16
—
end of the phrase
we need a shared glossary
3 of 3
12
1.9%
12
—
end of the phrase
minBranchWidth={0} — strictly proportional ribbons. The 8-mention “clarity” branch is 8/639 of the 18px scale, which is 0.23px: gone. The default 1.5px floor paints it nearly seven times its true share to keep it findable, and the printed count is unaffected either way — the trade is discoverability against arithmetic, and the number never moves.
Retro notes · what follows “we need”No floor · width is exactly share
639 mentions · 8 of 12 continuations drawn · 23 rows · 4 words deep
1 folded · 25 behind them
Word tree for we need: 639 mentions across 27 phrases, continuing into 12 distinct next words, of which 8 are drawn to the right over 23 rows and 4 words deep. Heaviest continuation to, 328 mentions, 51.3%. 1 word is still folded, holding 25 mentions. 3 phrases do not contain the term at all. Every drawn continuation is listed in the table that follows.
we need639
Ribbon thickness is that continuation’s share of we need, on one scale for the whole picture; the exact figure is printed beside every word. Branches leaving a fork stack across the trunk they come out of, so the unused part of a trunk is the phrases that stop there. Click a word — or press Enter on it — to make it the new root; the path above walks back.
481 mentions carry on past the 4-word depth this tree follows. Raise maxDepth to keep going, or re-root further along to pick the phrase back up.
3 of 30 phrases never say we need, so they are not drawn. Occurrences are counted per mention: a phrase saying it twice contributes two branches.
Every continuation currently drawn from we need, with how many occurrences take it, its share of the root, how many phrases stop there and what is still folded behind it.
Continuation
Word
mentions
Share
Stops here
Folded behind it
State
we need to
1 of 4
328
51.3%
—
—
open
we need a
1 of 4
87
13.6%
—
—
open
we need more
1 of 4
82
12.8%
—
—
open
we need better
1 of 4
70
11%
—
—
open
we need your
1 of 4
30
4.7%
—
—
open
we need this
1 of 4
9
1.4%
9
—
end of the phrase
we need clarity
1 of 4
8
1.3%
—
—
open
+5 rarer, under we need
1 of 4
25
3.9%
—
5 continuations, 25
grouped, not re-rootable
we need to fix
2 of 4
138
21.6%
—
—
open
we need to ship
2 of 4
95
14.9%
—
—
open
we need to talk
2 of 4
51
8%
—
—
open
we need to hire
2 of 4
26
4.1%
—
—
open
we need to write
2 of 4
18
2.8%
—
—
open
we need to fix the
3 of 4
138
21.6%
—
—
open
we need to fix the flaky
4 of 4
64
10%
64
—
end of the phrase
we need to fix the onboarding
4 of 4
41
6.4%
41
—
end of the phrase
we need to fix the billing
4 of 4
33
5.2%
33
—
end of the phrase
we need to ship the
3 of 4
95
14.9%
—
—
open
we need to ship the export
4 of 4
58
9.1%
58
—
end of the phrase
we need to ship the mobile
4 of 4
37
5.8%
37
—
end of the phrase
we need a proper
2 of 4
44
6.9%
—
—
open
we need a second
2 of 4
31
4.9%
—
—
open
we need a shared
2 of 4
12
1.9%
—
—
open
we need more time
2 of 4
39
6.1%
—
—
open
we need more examples
2 of 4
27
4.2%
—
—
open
we need more headcount
2 of 4
16
2.5%
—
—
open
we need better error
2 of 4
35
5.5%
—
—
open
we need better dashboards
2 of 4
21
3.3%
—
—
open
we need better docs
2 of 4
14
2.2%
14
—
end of the phrase
we need to talk about
3 of 4
51
8%
—
—
open
we need to talk about pricing
4 of 4
29
4.5%
29
—
end of the phrase
we need to talk about the
4 of 4
22
3.4%
22
—
end of the phrase
we need a proper status
3 of 4
44
6.9%
—
—
open
we need a proper status page
4 of 4
44
6.9%
44
—
end of the phrase
we need more time to
3 of 4
39
6.1%
—
—
open
we need more time to test
4 of 4
39
6.1%
39
—
end of the phrase
we need better error messages
3 of 4
35
5.5%
—
—
open
we need better error messages in
4 of 4
35
5.5%
35
—
end of the phrase
we need a second on-call
3 of 4
31
4.9%
—
—
open
we need a second on-call rotation
4 of 4
31
4.9%
31
—
end of the phrase
we need your approval
2 of 4
19
3%
—
—
open
we need your team
2 of 4
11
1.7%
—
—
open
we need more examples in
3 of 4
27
4.2%
—
—
open
we need more examples in the
4 of 4
27
4.2%
27
—
end of the phrase
we need to hire another
3 of 4
26
4.1%
—
—
open
we need to hire another reviewer
4 of 4
26
4.1%
26
—
end of the phrase
we need better dashboards for
3 of 4
21
3.3%
—
—
open
we need better dashboards for the
4 of 4
21
3.3%
21
—
end of the phrase
we need your approval on
3 of 4
19
3%
—
—
open
we need your approval on the
4 of 4
19
3%
19
—
end of the phrase
we need to write the
3 of 4
18
2.8%
—
—
open
we need to write the migration
4 of 4
18
2.8%
18
—
end of the phrase
we need more headcount on
3 of 4
16
2.5%
—
—
open
we need more headcount on support
4 of 4
16
2.5%
16
—
end of the phrase
we need a shared glossary
3 of 4
12
1.9%
—
—
open
we need a shared glossary for
4 of 4
12
1.9%
12
—
end of the phrase
we need your team to
3 of 4
11
1.7%
—
—
open
we need your team to review
4 of 4
11
1.7%
11
—
end of the phrase
we need clarity on
2 of 4
8
1.3%
—
—
open
we need clarity on the
3 of 4
8
1.3%
—
—
open
we need clarity on the deprecation
4 of 4
8
1.3%
8
—
end of the phrase
Degenerate corpus — nine rows the schema itself would refuse, because props are types and not a guarantee: this is what reaches a component whose feed was never parsed. Eight usable occurrences survive and every casualty is counted on the card: one phrase with no words in it, one NaN count, one repeated id, one note that never says the term, one sentence that says it twice (two branches, on purpose), two casings of “breathe” where the commoner one is the one drawn, and a 34-character word that no column can fit and that elides with its full text in the tooltip.
Messy corpus · every casualty countedBlanks, NaN counts, a repeated id, a repeated root and an unfittable word
8 mentions · 2 of 2 continuations drawn · 4 rows · 4 words deep
Word tree for we need: 8 mentions across 5 phrases, continuing into 2 distinct next words, of which 2 are drawn to the right over 4 rows and 4 words deep. Heaviest continuation to, 6 mentions, 75%. 1 stop right there. 1 phrase does not contain the term at all. Every drawn continuation is listed in the table that follows.
we need8
Ribbon thickness is that continuation’s share of we need, on one scale for the whole picture; the exact figure is printed beside every word. Branches leaving a fork stack across the trunk they come out of, so the unused part of a trunk is the phrases that stop there. Click a word — or press Enter on it — to make it the new root; the path above walks back.
1 mentions carry on past the 4-word depth this tree follows. Raise maxDepth to keep going, or re-root further along to pick the phrase back up.
1 of 6 phrases never say we need, so they are not drawn. Occurrences are counted per mention: a phrase saying it twice contributes two branches.
3 phrases were left out — 2 with no readable text or no usable count, 1 repeating an id an earlier phrase already claimed.
Every continuation currently drawn from we need, with how many occurrences take it, its share of the root, how many phrases stop there and what is still folded behind it.
Continuation
Word
mentions
Share
Stops here
Folded behind it
State
we need to
1 of 4
6
75%
—
—
open
we need we
1 of 4
1
12.5%
—
—
open
we need to Breathe
2 of 4
5
62.5%
1
—
open
we need to stop
2 of 4
1
12.5%
—
—
open
we need to Breathe properly
3 of 4
3
37.5%
3
—
end of the phrase
we need to Breathe supercalifragilisticexpialidocious
3 of 4
1
12.5%
—
—
open
we need we need
2 of 4
1
12.5%
—
—
open
we need to stop repeating
3 of 4
1
12.5%
—
—
open
we need to Breathe supercalifragilisticexpialidocious air
4 of 4
1
12.5%
1
—
end of the phrase
we need we need to
3 of 4
1
12.5%
—
—
open
we need to stop repeating ourselves
4 of 4
1
12.5%
1
—
end of the phrase
we need we need to stop
4 of 4
1
12.5%
1
—
end of the phrase
status="loading" · a skeleton in the tree’s own shape — root, then three widening columns. aria-hidden, no timers, and the pulse stops under prefers-reduced-motion.
Retro notes · what follows “we need”30 retro notes · counts are mentions, not notes
Loading phrases
status="empty" · a valid contract with no phrases at all, told apart from a corpus that simply never says the term.
Retro notes · what follows “we need”30 retro notes · counts are mentions, not notes
No phrases yet
A word tree reads whole sentences, so it needs the raw text — not a count per word. Branches appear as soon as the first phrase mentions the term.
status="error" · the fetch failed. “Try again” appears only when onRetry is passed, and clicking it flips to ready.
Retro notes · what follows “we need”The corpus query timed out
Couldn’t load these phrases
The data source didn’t respond.
Refusal · status is "ready" and the data is fine, but not one of the 30 notes contains “we must”. That is a different story from an empty corpus, so it gets its own sentence and says how many phrases it read.
Retro notes · what follows “we must”The term is spelled differently everywhere in this corpus
This word tree can’t be drawn
None of the 30 readable phrases contain “we must”.
Matching is case-insensitive and ignores punctuation at the edges of a word, but the whole term has to appear as consecutive words.
Zyeon UI