Lesson 1 of 8 · 8 min read · last verified 2026-08-26
Whose work is it?
In this lesson you will:
- Distinguish assistance from substitution in your own work
- Apply a defensibility test before putting your name to output
This module is about the judgements the previous seven have been circling. It starts with the one people ask about most, and get least help with.
You used an assistant. Is the result yours?
Not a question about tools
The unhelpful framing is a list of permitted tools. Spellcheck, fine. Grammarly, fine. An assistant, suspicious.
That line is arbitrary and everyone knows it. The tools blur, they are built into the software you already use, and a rule based on which product you opened will not survive the next release.
The useful question is not what you used. It is what you hold.
The defensibility test
Can you explain every significant choice in this, and defend it if challenged?
That is the line. Not how much you typed.
If you can explain why the argument is structured this way, why this evidence and not that, why this conclusion — you authored it, whatever helped you write it down.
If parts of it are there because they appeared and looked right, you did not. You are the person whose name is on it, which is a different thing, and the difference will show up the first time someone asks a question.
This scales. A routine email needs almost nothing. A board paper needs you to defend every number. Code you will maintain needs you to understand every branch.
Where it actually bites
Assessed work. If you are being examined, the work is evidence of your understanding. Substituting for it defeats the purpose and usually breaks explicit rules — and rules aside, you are the one who ends up without the understanding you paid to acquire.
Analysis you will be asked about. The meeting where you present it is the test. E4·L8 called this “the difficulty is the point”, and this is where it costs most visibly.
Anything you will build on. Work you do not understand becomes a foundation you cannot inspect. That compounds quietly and expensively.
Creative work presented as personal. The implied claim is that it came from you. If it did not, the claim is the problem, not the tool.
The honest grey area
Some cases genuinely are not clear, and it is worth admitting it rather than pretending the test resolves everything.
You had the idea, an assistant found the words. You wrote the draft, it restructured. It suggested a direction you would not have found, and you recognised it as right — is recognising it enough?
Reasonable people differ. The test still helps, because it asks something answerable: could you defend the choices? Sometimes recognising a good idea is the contribution. Sometimes it means you are steering something you do not understand.
Nobody can settle that for you. What you can do is stop pretending the question did not come up.
Try it now (6 minutes)
Take something you produced with an assistant recently. Pick three specific choices in it — a structural decision, a claim, a phrasing.
Can you say why each is that way? If not, that is not guilt — it is the map of where to look before this goes anywhere that matters.
Check your understanding
Recap
Authorship is not about which tool you used but whether you can explain and defend every significant choice. The line bites hardest on assessed work, analysis you will be questioned on, and anything you will build upon. Some cases are genuinely unclear — the failure is not being unsure, it is not noticing the question.
🗂 3 flashcards from this lesson join your daily review.