# Continuity & IP retention checklist

A short practice you can run after any AI or coding session. Goal: keep a verifiable record of what you produced, where it lives, and that nothing critical vanished overnight.

## After each working session
1. **Snapshot the work product** — Export or copy the final prompt/output (or commit) into a dated folder you control, e.g. `YYYY-MM-DD-topic/`.
2. **Hash the important files** — Note SHA-256 for key docs, configs, and repo archives so you can prove later if a byte changed.
3. **Record source & destination** — One line: what tool you used, what you asked for, where the result was saved (local path, repo, cloud).
4. **Check remote vs local** — If GitHub/Cloudflare/Drive is involved, confirm the remote still matches your local copy before you close the laptop.

## Weekly (15 minutes)
5. **Inventory critical repos** — List active repos and last-commit dates; flag anything you did not expect to change.
6. **Retention folder audit** — Confirm dated snapshots from the week are still present and readable.
7. **Access log glance** — Review recent collaborator/access events on GitHub (or equivalent) for unfamiliar actors.

## Red flags worth logging immediately
- File or commit present yesterday, gone today, with no intentional delete
- Output that contradicts a prior session without you changing the ask
- Config (e.g. Cloudflare) that differs from your saved baseline
- Repo history rewritten (force-push, missing commits) you did not authorize

## Minimal log template
```
Date:
Tool / session:
Artifacts saved (paths):
Hashes (file → SHA-256):
Remote checked (Y/N):
Anomalies:
```

Keep this log outside any single vendor's chat history so continuity does not depend on one product remembering you.