Answers as narrated walkthroughs

Where an answer explains something — how a flow goes through the code, what a change does, how two variants differ — it comes as a short walkthrough with slides and narration instead of a block of text, and it starts to play while the agent is still writing it.

The project: seven workstreams

W1The live walkthroughSlide format, hand-over slide by slide, voicing sentence by sentence with the playing player first, player under the question served through Obeya's server, answer slides in above it. Built on the branch of the prototype “B Obeyas eigener Walkthrough”.
→
W2“Show as walkthrough” everywhereObeya's sheet, Question cards, card conversations; a direct answer first gets a thread; a first-use hint.
→
W3A pointer word by wordWord times from Parakeet's hearing-back; diagrams build up as narrated.
→
W4Checks while the agent writesLines exist, slide not too full, narration doesn't just read out — fed back so the agent revises.
→
W5Phone, no voice, restartPlayer on the phone; captions at reading pace without a voice; voicing survives a restart.
→
W6The walkthrough's lookSlides and player modelled on showntell: slide design, a progress bar in one segment per slide, captions to read along, on and off with one click.
W7The demo videos' player in the same lookAfter W6. Demos on the card and on shared pages: one segment per chapter, the same read-along captions.

W2–W6 build on W1 and can run side by side after it; W7 follows W6. Each workstream updates its design chapters in the same change.

What the prototype measured

7–12 sfrom “Show as walkthrough” to first sound, starting by itself
20–30 sto the first slide for a new question; sound 2–5 s later
2 of 3questions the agent chose to answer as a walkthrough itself

Decisions