t2-p2-01authored3–5h

Design doc, written before any code

Spec

One page covering how you will handle task-assignment notifications (synchronous API call vs async queue) and how you will store activity history (event log table vs mutable fields plus audit table), with your reasoning. Commit it at docs/design-p2.md before writing the implementation.

Why this matters

"Design first" is normally unenforceable advice. Here git makes it falsifiable - the design commit must precede the implementation commit. That constraint is the whole lesson: a design written after the code is a description, not a decision.

Verify

No result yet. Run `learn verify t2-p2-01` locally, or push to trigger CI.

artifactartifact: docs/design-p2.md

unrun

reporepo: commit_precedes

unrun

judgejudge: docs/design-p2.md

unrun

Rubric

# t2-p2-01 — Design doc, written before any code

**Task:** One page covering how you will handle task-assignment notifications (synchronous API call vs async queue) and how you will store activity history (event log table vs mutable fields plus audit table), with your reasoning. Commit it at docs/design-p2.md before writing the implementation.

**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.

- Is a real tradeoff made, with a rejected option and a reason?

**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.