10 / 12 · Workflow tutorial
The tutorial gives an existing site a second request, then shows its revised expense view. Keeping the request and the artifact together makes user control part of the demonstration.
Official source: Build a Shareable Site ↗
01 / A sentence, inspected closely
Select a word to see its corresponding source frame. Use the arrow keys within the word buttons to step through. Frames may stay similar when a shot holds.
“add receipts, and see what they owe.”
Reading · interpretation
The first two word frames show the completed revision request in the composer and the earlier expense view to its right. The requested receipt support is visible as text; an actual receipt upload is not shown in these frames.
These seven machine-transcribed words agree with the available caption passage. The full comparison contains errors and disagreements elsewhere, especially product names and several dictated phrases. This short excerpt's onsets are still machine estimates.
The first two word frames show the completed revision request in the composer and the earlier expense view to its right. The requested receipt support is visible as text; an actual receipt upload is not shown in these frames.
By these word onsets, the composition has moved to the updated expense page. Summary amounts occupy the top of the result, with the request and response beside them. The transition joins an instruction to an inspectable output without showing all the intervening work.
The revised expense view stays visible through the end of the clause. Its totals and rows give the statement a concrete referent. Their presence demonstrates the displayed artifact, not the independent correctness of its arithmetic.
02 / Directing attention
A frontal desk view and a closer three-quarter angle handle explanation and transitions between examples. When the demo matters, the software becomes the main image and the presenter remains in a small upper-right inset.
The first long dictated request holds a close software view with trip details above the input waveform. It is a sustained context-and-input composition, rather than a separate shot for every requested feature. The written prompt appears after dictation finishes.
During revision, the request occupies the left and the site occupies the right. The wider result view lets the audience connect the requested expense behavior to the visible summary. The small presenter inset briefly disappears around the change, leaving the interface as the focus.
03 / Beyond the excerpt
An opening introduction promises a usable website and previews a trip site. The tutorial then returns to the presenter, explains the context and dictates a detailed building request over the actual composer. A site appears, followed by a second request about shared expenses and a revised expense view. Sharing is introduced as another decision, and a professional dashboard extends the use case to recurring work. The closing locates the sites and their links. The first preview and later trip example have different titles and designs: this is an edited tutorial organized by a use case, not one uninterrupted record of a single build.
Passage boundaries below are approximate. Speech is paraphrased; the word explorer above contains the short quotation. Editorial jobs are interpretations.
The presenter introduces website building through a group-trip use case.
An overhead arrival and laptop detail lead into the presenter, then a browser preview of a trip site and its itinerary.
Editorial job · Show the kind of destination before explaining how to request it.
The explanation identifies the app, available trip context and dictation as the input method.
Frontal and three-quarter presenter views carry the setup.
Editorial job · Establish the starting conditions for the demonstration.
A detailed request specifies the trip site's information, activities, expenses and review before sharing.
Trip details remain above a recording waveform; the dictated request later appears as composer text.
Editorial job · Make the request concrete while preserving its source context.
The explanation describes hosting, stored information and the ability to ask for changes without writing code.
The view widens through a building state and a site preview, then returns to the presenter.
Editorial job · Connect the request to an emerging artifact and introduce iteration.
A second instruction asks for expense splitting, individual amounts and receipts; the narration describes the resulting shared activity.
The existing expense page sits beside the recorded request, followed by a reframed view of the updated expense summary.
Editorial job · Make revision an observable part of the workflow.
The presenter explains private, selective and public sharing and asks for the trip group to receive access.
The presenter gives way to a typed sharing request beside the site.
Editorial job · Treat distribution as a separate decision after creation.
A product-launch dashboard introduces a professional use case that combines metrics, team information and public feedback.
Alternating presenter views explain the new purpose before the interface returns.
Editorial job · Broaden the application through another specific need.
A recurring-update request names sources and a schedule, followed by an explanation of finding sites and their links.
The dashboard's composer records and displays the instruction, then the Sites list and sharing dialog appear.
Editorial job · Show how the artifact is requested, found and shared.
The closing joins group planning and an ongoing dashboard as two uses of the same capability.
The presenter returns before the closing typography and mark.
Editorial job · Resolve the two examples into a concise product proposition.
04 / Check the actual image change
These pairs use neighboring decoded source frames. Their timestamps are frame evidence; they do not make the speech alignment exact.
The presenter fills the main image at 32.032 seconds. At 32.074 the software takes over, with trip details above the recording waveform and the presenter in an inset. The composition changes as the general explanation becomes a specific instruction.
Watch around this transition ↗
The earlier expense layout and completed request are visible at 72.906 seconds. At 72.948 an updated view appears within a brief blurred reframe, which continues through the neighboring frames. This is an edited change of state and framing, not continuous evidence of the time needed to perform the revision.
Watch around this transition ↗Proposed use in the all-hands
Build a demo around an initial artifact, one meaningful revision and a result the audience can inspect. Hold the request's context during dictation, then give the changed output enough space and time. Verify the actual Poe behavior, including sharing or scheduled execution, whenever the recorded claim depends on it.
Open the storyboard worksheet →Scope of the reading
The inspected images show a revision request, a changed expense page, a sharing request and a scheduling request. They do not establish recipient access, a future scheduled run, receipt-upload success, calculation correctness or real build latency. The source's presenter inset does not change the all-hands requirement for separate talking-head and presentation videos.
The full machine transcript was read; 479 estimated words were mapped to source frames. The visual review inspected 281 half-second sample positions, the 7 selected word frames and these 2 native transition windows. Available caption differences were checked. No continuous playback or human listening verification. Method and timing limits.
The earlier reading in the latest-100 study · Structured close readings