# save (10-save.com)

People say "save" to keep something so they do not lose it. They mean storing a file, preserving a memory, or setting money aside. It is about holding onto what matters.

## What a model may hear
- persist to disk (databases and file systems): write data to permanent storage, possibly overwriting existing files without warning
- save checkpoint (machine learning training): serialize model weights and optimizer state to resume training later
- save game state (game development): serialize player progress to a slot or cloud storage
- HTTP 302 save (web browsers and forms): prompt user to download a file rather than display it
- save register (CPU architecture and assembly): preserve a register value onto the stack before a function call

## Where people and models part ways
- Says: "Save my work."
  Means: Keep my document safe.
  May be taken as: The model may overwrite the previous version without a backup, or save to an unexpected path.
  Say instead: "Save my work as a new file and keep the old version too."
- Says: "Save everything I said."
  Means: Remember this conversation.
  May be taken as: The model may assume you mean write to an external database or file, which it cannot do.
  Say instead: "Include everything from this conversation in your context for our next exchange."
- Says: "Save me time."
  Means: Make this faster for me.
  May be taken as: The model may interpret this as a request to batch or automate in ways that skip confirmation steps.
  Say instead: "Give me the quickest way to do this, and confirm each step with me first."
- Says: "Save the results."
  Means: Keep the output for later.
  May be taken as: The model may generate a download link or file path it cannot actually create.
  Say instead: "Show me the results so I can copy them, or tell me how to export them myself."

## Tips
- Say where you want something saved if it matters to you.
- Ask for a backup or version history if you do not want to lose the old copy.
- Do not assume the model can save to your computer or the cloud; ask what it can do.
- Use "store" or "remember" if you mean keep in mind, not write to disk.
- Say "export" or "download" if you need a file you can take with you.

## Often confused with
- store: More often means keep in memory or a data structure, not necessarily persist.
- commit: A deliberate, often irreversible save in version control.
- cache: Temporary storage that may be discarded, not trusted permanence.
- archive: Long-term storage, often compressed and harder to access quickly.
- backup: A copy kept for recovery, not the working copy.
- persist: Technical term for making data survive after a process ends.