What is backed up, and what is not
The question people ask too late
There is no single good answer to "is it backed up?". There is one answer per object, and it changes what you have to do with your own hands.
A deleted conversation is gone: the line says so plainly.
| Object | Lifetime | What to do |
|---|---|---|
| Filed documents | As long as they sit in a space | Nothing: they live in your space, backed up with it. |
| Conversations | Kept | Nothing, but it is not a filing cabinet: what matters gets filed. |
| Artefacts | One month | Download them. A spreadsheet you never picked up is lost. |
| Memory | Until you clear it | Re-read now and then what it has retained. |
| Service keys | Until revoked | They cannot be read back: lost, you mint a new one. |
The only real possible loss is a forgotten artefact. Everything else lives in your space, and your space is backed up. A costing produced on a Tuesday and left there is gone after a month, not out of negligence, but because a draft left lying around eventually gets mistaken for the current version.
What backing up does not protect
A backup gives you a file back as it was. It does not say whether it was right. A wrong quotation, faithfully backed up, is still a wrong quotation, hence this course's insistence on checking what commits you.
The joinery's habit
At the Ateliers du Vent d'Ouest the rule fits in one sentence pinned near Farida's desk: "anything that goes out to a customer gets downloaded and filed". The rest can live in the conversation.
In closing
There is no general answer to "is it backed up?", there is an answer per object. Remember the ones that concern you: they decide what you must copy with your own hand.
Commenting is not enabled on this course.