You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Part of #336. Decided 5 September 2026 and closed; the build is #517.
Question
The design's second guide piece: event-driven micro-tips. Which exist and with what copy, what fires each, how dismissal is stored, and how they order against the Today tour.
Ruling
All seven ship, copy verbatim from prototype/guide.jsx:91-98. Checked against each destination screen in the app: none of them repeats what the screen already says; each carries a rule the learner cannot read off the screen (the unlock order and the diamonds on Path, the 48-hour window and the stamp, that only lessons grow the tree, the ribbon, how terms join the Dictionary, the 7-day freeze rule, that the Studio's look applies everywhere).
Triggers as designed (prototype/app.jsx:1196-1214): place tips on first visit to Path, the Dictionary and the unlocked Studio; the save tip after the first save; the challenge, tree and freeze tips on the Learn tab, in that order, each following a beat the learner just saw. Never inside a lesson, never under the tour or a gate sheet. Every tip is dismissable and shows once ever.
Pacing as designed: one at a time, seen on show, 12 s between tips on the same screen, a short beat on a screen change, and the tour finishing counts as "just shown".
Persistence follows tourSeen, not the design. The prototype keeps the seen list in a progress-scoped store that Reset progress wipes. The app already ruled that "already introduced" is not progress: tourSeen sits on the device-local settings row, survives Reset and goes with Delete account. The tips' seen list lives beside it under the same rule. Rulings beat the prototype (docs/README precedence).
Part of #336. Decided 5 September 2026 and closed; the build is #517.
Question
The design's second guide piece: event-driven micro-tips. Which exist and with what copy, what fires each, how dismissal is stored, and how they order against the Today tour.
Ruling
prototype/guide.jsx:91-98. Checked against each destination screen in the app: none of them repeats what the screen already says; each carries a rule the learner cannot read off the screen (the unlock order and the diamonds on Path, the 48-hour window and the stamp, that only lessons grow the tree, the ribbon, how terms join the Dictionary, the 7-day freeze rule, that the Studio's look applies everywhere).prototype/app.jsx:1196-1214): place tips on first visit to Path, the Dictionary and the unlocked Studio; the save tip after the first save; the challenge, tree and freeze tips on the Learn tab, in that order, each following a beat the learner just saw. Never inside a lesson, never under the tour or a gate sheet. Every tip is dismissable and shows once ever.tourSeen, not the design. The prototype keeps the seen list in a progress-scoped store that Reset progress wipes. The app already ruled that "already introduced" is not progress:tourSeensits on the device-local settings row, survives Reset and goes with Delete account. The tips' seen list lives beside it under the same rule. Rulings beat the prototype (docs/README precedence).