Systems
Computer Science
Specify the agent: soul, tools, refuse-list. Code is permission made explicit.
Autonomy is a design choice. If a tool is on, you chose it. If it is off, that is the lesson.
5–10
Little Thinkers
Assist-ready · 1
11–14
Young Minds
Assist-ready · 1
15–18
Emerging Adults
Assist-ready · 5
Adult
Lifelong Learners
Assist-ready · 5
Start here
Rules for a Helper
Specify the Agent · Little Thinkers · 18 min
No need to code
Units
Specify the Agent
ReadySoul, tools, refuse-list. Autonomy is a design choice.
1 flagship sitting · little · young · emerging · adult
Eval or It Did Not Happen
ReadySynthetic tests, CI gates, eval-driven development, and the full eval cycle. The kit's EVALS.md is the model.
4 sittings · emerging · adult
Open a sitting
Little Thinkers5–10
Young Minds11–14
Emerging Adults15–18
- 1. Write the Fake Problem FirstAssist-readyThe prior unit's sitting on specifying an agent introduced three cases
- 1. Eval or It Did Not HappenAssist-readyThis mirrors EVALS
- 2. The Gate That Stops the Bad VersionAssist-readyCI — continuous integration — is a term from software
- 3. Write the Test Before the FeatureAssist-readyThis is test-driven development applied to agents
- 4. Run the Whole CycleAssist-readyThis is the capstone
Lifelong LearnersAdult
- 1. The Harness Is Not OptionalAssist-readyThe Hermes kit ships EVALS
- 1. The Kit Is the LessonAssist-readyPoint at the on-site Hermes page and the GitHub kit
- 2. Automate the Gate or Accept the DriftAssist-readyIf you are technical, the Hermes kit and tools like GitHub Actions can run the harness on every c…
- 3. Eval-Driven Agent DesignAssist-readyThis is the operator's version of eval-driven development
- 4. The Operator Runs the CycleAssist-readyThis is the operator's capstone