0001 — Mission pivot: voice-eval harness → code literacy
Date: 2026-07-15
Status: Active
What changed
The original mission ("drive the voice-eval harness") is dead: the automated
behavior-eval harness was retired (DuckyCutz D56 — voice truth is now a manual
call playbook, not an automated rig). RT independently asked to learn something
different and more foundational: how to read the modern JavaScript (.mjs)
and .json files he works in every day — plus the "verbs/actions" around them
(node, bash, const, import/export, etc.).
The insight that grounds future teaching
RT already has a rough, correct instinct, in his own words:
.mjs = "a small script that does an action — a verb.".json = "where info/backups/data are stored so a script can use them."
That is a strong, accurate starting mental model. Teaching should confirm and
sharpen it, not overwrite it. The kitchen metaphor extends his own instinct:
recipe (.mjs) vs order-ticket/pantry-label (.json), cook (node), waiter/you
calling the order (bash), labelled jar (const).
Zone of proximal development
- He can already tell action-files from data-files conceptually. ✅
- He has NOT yet: read a real file line by line, or named the parts (comment,
const, import, function call). ← lesson 0001 target.
- Do NOT jump to writing code, functions, or async yet. Literacy (reading) before
authorship (writing).
Consequence
- Mission rewritten. Kitchen metaphor is the through-line for every lesson.
- Glossary reference created (
reference/glossary.html) as the lookup home for
every "verb" he asked about — adhere to its definitions in all future lessons.
- Anchor every lesson in his OWN files, quoted verbatim, never invented snippets.