System brief

The module

Lesson, exercise and rubric

• Read the lesson
• Do the exercise
• Check it against the rubric

Open the repository in a coding agent and run /module 01 for a Socratic session over this stage.

What you leave behind · markdown

System brief

Required sections:

• user and job
• in scope
• explicitly out of scope
• success measure
• kill criterion

May appear on a public portfolio once redacted: remove employer name, customer name.

The eval · eval:system-brief-complete

The brief names a job and a way to be wrong

1. has-out-of-scopeAn explicit out-of-scope section exists and is not empty. Checked by: Parse headings; the out-of-scope section has at least two bullets.
2. has-kill-criterionA condition is stated under which the project would be stopped. Checked by: The kill-criterion section contains a measurable threshold or date.

Every check must pass. There is no partial credit and no override.

Evidence that counts

Proof has to exist outside your own claim.

At least 1 of: a commit or file a third party can open; a recorded, reproducible eval run. Evidence older than 365 days is stale and does not count.