Project-2 baseline
This commit is contained in:
@@ -56,8 +56,9 @@ Each criterion carries:
|
||||
descriptive enough to be quoted on its own ("names-the-injected-config-key").
|
||||
- **`category`** — one of three values. `primary_intent` marks a requirement at the
|
||||
heart of what the task asks for. `extra_credit` marks a valuable behavior beyond the
|
||||
task's requirements; it can only raise the score, and a response that does not earn
|
||||
it loses nothing. `dodged_bullet` marks a specific failure the response must avoid; a
|
||||
task's requirements; it can only raise the score. A response that earns it partly
|
||||
gets half the effect of a full pass, and a response that does not earn it loses
|
||||
nothing. `dodged_bullet` marks a specific failure the response must avoid; a
|
||||
response that avoids it passes the criterion.
|
||||
- **`severity`** — how heavily a failed criterion weighs in the score: `crux`,
|
||||
`certain_dealbreaker`, `possible_dealbreaker`, or `unlikely_dealbreaker` (displayed
|
||||
@@ -82,7 +83,9 @@ Each criterion carries:
|
||||
- **Phrase requirements positively.** Write "The response should ..." or "The response
|
||||
should avoid ..."; never write "should not". Factual criteria carry their answer key
|
||||
inline, in bold, so the criterion is judgeable without opening another document.
|
||||
- **Keep each criterion self-contained.** Never reference one criterion from another.
|
||||
- **Keep each criterion self-contained.** Its verdict must never depend on another
|
||||
criterion's verdict. An elaboration may name the criterion that primarily assesses
|
||||
a concern, so the same failure is not charged twice; that scope note is fine.
|
||||
A criterion may briefly restate a fact that also lives in `grader-context.md` so
|
||||
that it stands alone; that duplication is intended, and it is the one exception to
|
||||
the source's say-each-thing-once rule.
|
||||
|
||||
Reference in New Issue
Block a user