Work / Trunk / Wiki / Surfaces
capture-walk-yourself
Surfacecanonicalverified 2026-10-19
SURFACE.WEB.ONBOARDING.CAPTURE-WALK-YOURSELFSummary
Walk it yourself, in every plan (2026-10-19-walk-free-automatic-team): the person uses their own product and Trunk captures each page they open. It is the free month's way to capture, from capture. Drawn on Team (moment 2) at Admin's 2FA step: chitragupt.ai's "Enter the code" page for admin@chitragupt.ai, with four of six digits typed. The totals continue from 10 pages.
Raw wireframe
- .context/designs/web/onboarding/capture-walk-yourself.html
- .context/designs/web/onboarding/capture-walk-yourself-loading.html — loading
Why it is drawn this way
The frame takes the room (owner, 2026-10-19). It runs edge to edge. The top bar says what is happening and holds Back, Back to automatic and Stop; there is no footer and no banner. A notice shows only while the product asks for a sign-in.
The product's frame holds only the product. The site being captured is a third party's. Trunk's notices sit above the frame. Nothing of Trunk's is drawn inside it, but for the loading cover while a page is analyzed.
The frame is a live session of the product. The person clicks in their own site. Opening a page is the act of capturing it, so there is no capture button.
Found so far fills as the walk goes. After each page, the worker works out what the capture will save at the end — pages, components, tokens, icons, links — and the totals and the list show it at once. To visit lists the pages the saved ones link to that nobody has opened; one opens in the frame with a click. Every link on a page read is noted, so the journey is whole without clicking each one.
A screen of its own, not a state. No word in the closed set of states means "a person is driving".
The frame is a hosted browser. The worker runs it and sends its picture; the person's pointer and keys are sent back. How, and its limits, are in features/0007-walk-it-yourself.md.
Drawn after the password. The moment of signing in is capture-sign-in; the code is typed into the product's own page, which is why only a person can capture Admin. Walking by hand is for a role the worker cannot sign in as, with 2FA or single sign-on; the password typed into the frame is not kept.
The frame's bar has Back, Forward and Reload, and the path can be typed. A walk often ends on a page with no way on; without them the only way out was to start again. The host is fixed: Go opens a path of the same product, never another site. The automatic walk shows a saved picture, not a live page, so its bar keeps the dots.
An action that leads to another site is refused. A click on LinkedIn, a mailto: link or a tab to another site leaves the person where they were: the walk stays on the product. Nothing is kept of it.
loading is a page being saved. It shows the moment a new page opens, not once it has settled. A scrim covers the whole left side, with one card: "Analyzing this page" and its address. The person waits, then the product is theirs again; a click while it is saved would go to a page that is still being read. The page is read in a copy opened beside theirs, at every size at once, so it is never marked, photographed or resized under them.
Related
Sources
- .context/designs/web/onboarding/capture-walk-yourself.html
- .context/designs/web/onboarding/capture-walk-yourself-loading.html — loading