Safety Net Playbook

What to add when risk is real

• A backup path that stores the important state in a second format.
• A visible alert when data is missing, stale, or partially loaded.
• A recovery action that the user can trigger without opening dev tools.
• A short audit note explaining what the feature protects and what it does not.

General prompt for future work

text
Add a backup/check layer for this feature so we do not lose user content or ship a broken state.
Keep it compact and non-sloppy. Prefer a recovery action, a clear alert, and a saved fallback.
Do not redesign the UI. Do not invent fake data. Preserve the current aesthetic.

Check list

• Does this feature have a saved fallback?
• Can the user recover without starting over?
• Does the UI say what went wrong in one short line?
• Is the backup path easy to find later?
• Can we verify the result with a build or quick test?

Good candidates

• revision pack exports
• cached drill queues
• course content loaders
• deploy-sensitive markdown routes
• local state that should survive refresh

Keep out

• noisy modal spam
• duplicate warning banners
• fake placeholders that look real
• big redesigns just to fit a safety note