t2-p3-07authored4–7h
Load test and capacity documentation
requires: t2-p3-06
Spec
Run a load test - k6 or Locust - against the deployed instance, document the breaking point, and write down the single highest-leverage optimisation if you needed ten times the traffic.
Why this matters
Naming one next optimisation forces a judgement about where the bottleneck actually is, rather than a list of everything that could theoretically be faster. Being wrong here is fine and instructive; being vague is not.
Verify
No result yet. Run `learn verify t2-p3-07` locally, or push to trigger CI.
artifact
unrun
evidence
unrun
judge
unrun
Rubric
# t2-p3-07 — Load test and capacity documentation
**Task:** Run a load test - k6 or Locust - against the deployed instance, document the breaking point, and write down the single highest-leverage optimisation if you needed ten times the traffic.
**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 the breaking point a measured number?
- Is exactly one next step named?
**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.