Resumable by default
A large upload is a sequence the server can rejoin, not a single request that either survives the whole way or is wasted. Progress is real, and a flaky connection is an inconvenience rather than a restart.
The storage frame
Uploads are resumable, so a dropped connection costs the remainder of a file rather than the whole of it. When a version completes it is sealed: later edits create a new version, and the old manifest keeps meaning exactly what it meant.
A large upload is a sequence the server can rejoin, not a single request that either survives the whole way or is wasted. Progress is real, and a flaky connection is an inconvenience rather than a restart.
Each completed version has its own manifest. Nothing rewrites history in place, so "the file changed" is always a new fact appended beside the old one rather than a silent overwrite.
Items go to Trash and come back with Restore. The destructive version of delete is a deliberate, separate act — not the thing that happens when someone mis-clicks a row.
Inside the console
Folders and files with size and modified date, and the row actions that matter — preview, download, rename, move, copy, share, link, trash — each one gated by a Drive permission check rather than by whether the button is on screen.
