t4-p3-05authored1–3h
Fast-versus-slow decision log
requires: t4-p3-04
Spec
Document at least 2 moments where you chose between shipping fast and being careful - for example skipping error handling on an API call to hit the launch date because the risk was low and reversible - with your reasoning for each call.
Why this matters
The reasoning is the artifact. "Low risk and reversible" is a defensible engineering judgement; "we were in a hurry" is not, and the distinction is what separates intentional debt from accident.
Verify
No result yet. Run `learn verify t4-p3-05` locally, or push to trigger CI.
artifact
unrun
judge
unrun
Rubric
# t4-p3-05 — Fast-versus-slow decision log
**Task:** Document at least 2 moments where you chose between shipping fast and being careful - for example skipping error handling on an API call to hit the launch date because the risk was low and reversible - with your reasoning for each call.
**Strong:** Directly answers every one of the review questions below in the affirmative, with specific evidence from the actual work, not a restatement of the task.
- Does each entry name what could go wrong and why that was acceptable?
**Passing but weak:** The deliverable exists and technically satisfies the spec, but is generic, restates the task instructions instead of engaging with them, or only partially addresses the review questions below.
**Fails:** The deliverable is missing, or engages with none of the review questions below - e.g. it describes what was built without explaining the reasoning the task actually asks for.