# Process Documentation Sheet

One page per project (or per session). This is the habit that makes AI use defensible, portfolio-safe, and actually educational. Used in every lab from Week 1; the spine of the Week 14 capstone write-up.

**Why bother:** process documentation is (1) your authorship evidence, (2) your disclosure source material, (3) how you learn what actually works, and (4) what employers increasingly ask to see.

---

## Project / date / track

## What I was trying to do
One sentence, before you started. (Write it first — it stops drift.)

## Tools used
Tool + version/tier if known. Include the boring ones (transcription, search).

## Key prompts (keep the real ones, verbatim)
The 1–3 prompts that mattered. Paste exactly — future-you needs the wording, not a summary.

## Iterations
How many generated/drafted: ___ How many survived: ___

## Rejections and why (the important part)
| # | What I rejected | Reason (specific) |
|---|---|---|
| 1 | | |
| 2 | | |
| 3 | | |

## Human decisions that shaped the result
Selection, edits, repairs, recombinations, the call nobody else would have made.

## What AI got wrong
Errors, genericness, hallucinations, drift — and how you caught each one.

## What I verified (and how)
Facts, sources, specs, licences checked. "Nothing needed checking" is rarely true.

## Disclosure draft
One sentence, written NOW while you remember the truth of it. (Pattern: AI did [tasks]; I did [decisions/craft].)

## What I'd do differently
The note future-you will actually thank you for.