data/sessions/explorer-nested-folders/memory.md

Memory: explorer-nested-folders

Overview

Build a multi-level folder tree and move a file into its deepest level, using the file manager's ribbon and context menus. Use this when a nested structure has to be created and populated by pointing. Each level is created from the ribbon's new-folder button, named, and opened before the next is created; the file is then cut from the top folder and pasted inside the innermost one. The recorded trace builds Projects\2026\Q3\ and moves report.pdf into Q3\.

Prerequisites

• A desktop environment with a file manager, or a shell.
• A starting folder that exists and is writable, and that is the active target when creation begins. The keyboard route creates each folder inside whatever container currently has focus, so the focused container — not the one on screen — is what governs.
• The full folder path decided in advance, level by level, including capitalisation.
• A file to relocate, existing and identifiable by name, and write access to both its current folder and the final destination.
• No existing folder at any level using the intended name, and no file of the same name at the destination.
• Clarity that the file is moved, not copied — nothing must remain at the source.
• Enough space, and both locations on the same volume where that can be arranged; a move across volumes copies and deletes rather than renaming.

Steps

Step 1 — Left-click at (85, 34)

The task is to build a three-level folder path and then move a file into its deepest level, so the first folder has to be created inside corpus-seed. Explorer is already showing that folder, but its ribbon is collapsed to a bare tab strip, so the New folder button is not on screen. Move the cursor and Left-click the Home tab to expand the ribbon and reveal it.

Step 2 — Left-click at (478, 85)

The ribbon is now expanded. Move the cursor and Left-click New folder. Explorer creates a folder named New folder and immediately puts its name into an inline edit box with the text selected, so the next thing typed replaces the name rather than appending to it.

Step 3 — Type: Projects

Type Projects while the name is still selected and in edit mode. The typed text replaces the placeholder name outright.

Step 4 — Press: Enter

After typing Projects Press Enter to commit the name. Until this happens the folder is still called New folder on disk, and clicking elsewhere would commit it under that name instead.

Step 5 — Double-click at (212, 197)

The next folder has to be created inside Projects, so the view has to descend into it. Projects sorts among the folders — after found, before shots — which puts it on the fourth row. Move the cursor and Double-click it to open it.

Step 6 — Left-click at (85, 34)

The view is now inside Projects, which is empty. The ribbon collapsed again when the folder was opened, so move the cursor and left-click Home to expand it once more. This repetition is inherent to the collapsed-ribbon route, not a mistake.

Step 7 — Left-click at (478, 85)

Move the cursor and Left-click New folder again, creating the second level with its name in edit mode.

Step 8 — Type: 2026

Type 2026 to name the second level.

Step 9 — Press: Enter

After typing 2026 Press Enter to commit the name.

Step 10 — Double-click at (212, 134)

Projects contains only 2026, so it is the first and only row. Move the cursor and Double-click it to descend to the second level.

Step 11 — Left-click at (85, 34)

Inside 2026, expand the ribbon again with the Home tab.

Step 12 — Left-click at (478, 85)

Move the cursor and Left-click New folder for the third and last level.

Step 13 — Type: Q3

Type Q3, completing Projects\2026\Q3\.

Step 14 — Press: Enter

After typing Q3 Press Enter to commit the name. The folder half of the task is now done; what remains is moving report.pdf into this folder.

Step 15 — Left-click at (93, 67)

report.pdf lives in corpus-seed, two levels above the current location, so the view has to go back up before the file can be picked up. Move the cursor and Left-click the Up arrow in the address bar to move from Projects\2026 to Projects. The Up button is used rather than a breadcrumb segment because its position does not change with the path, whereas breadcrumb segments shift with the length of the folder names.

Step 16 — Left-click at (93, 67)

Move the cursor and Left-click Up a second time to arrive back at corpus-seed.

Step 17 — Right-click at (212, 407)

Move the cursor and Right-click report.pdf to open its context menu. It now sits one row lower than it did at the start of the take: creating Projects inserted a folder above all the files, and folders sort above files. Right-clicking both selects the file and opens the menu in one action.

Step 18 — Left-click at (280, 640)

Move the cursor and Left-click Cut. This marks the file for relocation rather than copying it, which is what "move" requires. The row stays visible in the listing afterwards — Windows does not remove it until the paste completes — so its continued presence is not a sign the cut failed.

Step 19 — Double-click at (212, 197)

A cut is completed by pasting at the destination, so the view has to travel back down to Q3. Move the cursor and Double-click Projects, still on the fourth row.

Step 20 — Double-click at (212, 134)

Move the cursor and Double-click 2026, the only item inside Projects.

Step 21 — Double-click at (212, 134)

Move the cursor and Double-click Q3, the only item inside 2026. The view is now at the destination.

Step 22 — Right-click at (700, 300)

Q3 is empty, so there is nothing to right-click on and the menu has to be opened from blank space in the file pane. Move the cursor and Right-click there to get the folder's own context menu, which is the one that carries Paste.

Step 23 — Left-click at (780, 439)

Move the cursor and Left-click Paste. It is black rather than dimmed, which confirms the clipboard still holds the cut file. This completes the move: report.pdf is removed from corpus-seed and appears in Projects\2026\Q3\.

Notes & Edge Cases

1. Each level has to exist before the next one can be made inside it, so the route alternates between creating a folder and descending into it. A single command that builds the whole path at once exists on the shell side; through the file manager the depth of the path is the number of times the same pair of steps repeats.
2. The ribbon collapses again every time a folder is opened. Re-expanding it before each new folder is inherent to this route rather than a mistake or a missed step, and a trace that looks repetitive here is correct.
3. A new folder arrives with its name in an inline edit box and the placeholder selected, so typing replaces it. Until the name is committed the folder exists on disk under the placeholder name, and clicking elsewhere commits it that way.
4. Creating a folder changes the row positions of everything below it. Folders sort above files, so a file that was on one row at the start of the task is a row lower afterwards — a coordinate read at the beginning is not valid at the end.
5. Navigate up with the control whose position does not move. Breadcrumb segments shift with the length of the folder names in the path, while the up control stays where it is regardless of how deep the path has become.
6. Cut marks the file rather than moving it; nothing has happened until the paste. The row also stays visible in the listing until then, so its continued presence is not a sign the first half failed.
7. In an empty destination there is nothing to right-click on, so the menu has to be opened from blank space in the file pane. That is the folder's own menu, which is the one that carries the paste entry — an item's menu does not.
8. A dimmed paste entry means the clipboard no longer holds the file. Reading it before clicking is the cheapest confirmation available, because the alternative is discovering it after several navigation steps.
9. The folder and file names here are for demonstration. Verify the real names, paths and locations against the machine the task is running on rather than reusing what the trace shows.