t2-p1-01authored2–4h
Repo setup with a layered structure
Spec
Initialise with a layered structure - routes/controllers, services, data access, models - and a .env-based config system. First commit is skeleton only, with a README describing the architecture decision and why you chose this layering.
Why this matters
Committing the skeleton and its rationale before any feature exists is what makes the layering survive contact with deadlines. Architecture written down after the fact is just a description of whatever happened.
Verify
No result yet. Run `learn verify t2-p1-01` locally, or push to trigger CI.
artifact
unrun
repo
unrun
repo
unrun
judge
unrun
Rubric
# t2-p1-01 — Repo setup with a layered structure
**Task:** Initialise with a layered structure - routes/controllers, services, data access, models - and a .env-based config system. First commit is skeleton only, with a README describing the architecture decision and why you chose this layering.
**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 the rationale name a real tradeoff, or restate the structure?
**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.