re0-tutorial

name: re0-tutorialdescription: "Learn one skill of the suite through three graded levels whose completion rests on the learner's own submission, never on an invocation trace."disable-model-invocation: true

Advance a human-chosen exercise through three levels, grade the learner's submitted work, and append a private attempt record.

Goal

Teach one skill's best practice, reasoning about combinations, and application to a real problem, in that order. Completion means only that the submitted exercise meets its contract. Human completion and transfer remain unmeasured; neither a simulated learner nor an invocation trace measures learning.

Workflow

1. Start only on human invocation. Agree on a target, level, and exercise identifier. Read the installed target skills and their contracts, including Verification. Choose skills for what they teach, without preferring an invocation lane. State the required submission and grading criteria before the learner begins.
2. Define the level using the table below. Explain the task and its trigger without performing the learner's steps, producing their submission, or supplying the L3 combination. Wait for the learner's work.
3. On resume, from this skill's folder run node scripts/attempt.mjs --exercise <id> --skills <skill folders...> [--json] with the exercise's skill folders. It digests them with line endings normalized, reads the exercise's records under .re0/tutorial/<exercise>/, compares the latest with the current installation, and prints a status (fresh, match, version-only, content-difference, stale or unreadable) with the next unused attempt path. Exit codes: 0 fresh, match or version-only, 3 content-difference or stale, 4 unreadable, 2 a usage error, which is a broken run: fix the command and run again. Apply the resume rules below to that status; do not silently substitute a renamed dependency.
4. Check that the submission is present and establish authorship, then grade against the level's criteria. Record the decisive evidence and reason. An invocation, actor label, or host trace supplies context only; it cannot establish learner performance or settle ambiguous authorship.
5. Write one new, immutable attempt record at the next path step 3 printed (.re0/tutorial/<exercise>/<version>-<attempt>.local.md); the script prints that path for a first attempt too. Report the grade, any clarification needed, and the record path. Only a completed grade earns an exercise-completion badge.

Grading

Apply these decisions in order so each submission receives exactly one grade:

1. A required artifact or account is absent: not-completed, no badge.
2. The agent produced the required work: not-completed, no badge; never "completed with help".
3. The submission is present but inconclusive, or learner authorship is unknown or ambiguous: not-completed with a pending-clarification note naming the specific learner evidence that would settle it, no badge. Do not infer an answer from traces.
4. Learner authorship is established and all level criteria pass: completed; the badge means only this exercise was completed. A conclusive failure of any criterion is not-completed, with its reason and no badge.

Local record and resume

Each record contains exercise, version, attempt, learner-action, evidence, and result; evidence is the learner's submitted artifact or account, preserved or durably referenced. Add actor and host-trace, explicitly labelled supporting context only, and a skill-set digest identifying installed skills and their content so changes to the exercise's dependencies can be distinguished from unrelated version changes. Include the level, dependency identities, grading citations, reasons, and any clarification or predecessor link needed to interpret the attempt.

The logbook is private to its owner, local to the machine, untracked under .re0/ and *.local*, and never shipped. Keep failed and abandoned attempts with their reasons. Never edit, overwrite, or delete an existing record. A duplicate resume of a recorded attempt gets a fresh record linked to the previous one, never a revision. Only new learner evidence can change a previous not-completed judgment in a subsequent record.

• If version and digest match, continue the exercise at its saved point. Continuing an unrecorded attempt does not create a duplicate; once a record exists, further recording uses a new attempt identifier.
• If only the installed version differs and the exercise's own skills are unchanged, resume with the difference noted in the new linked record. The version difference alone neither passes nor fails the submission.
• On ordinary resume, if a dependency keeps its name but its installed content differs from the recorded skill-set digest, preserve the prior record and note the content difference in a new linked attempt record. If the exercise's quoted Verification passage remains verbatim in the current skill body, resume and grade against that passage. If the passage is absent, the required text is missing: classify the prior attempt as stale under the stale rule and open a new version-marked attempt without a badge.
• If a dependency was renamed, retired, or is missing, classify the prior attempt as stale in a new current-version attempt record referencing it. Leave the prior file intact, including its original version and result, and open the new exercise attempt without a badge. Do not remap the old exercise onto a renamed skill or grade it as though the dependency still existed.
• Interruption records incomplete, distinct from failed. Continue an interrupted exercise only if the version matches; otherwise open a new version-marked attempt. This interruption rule takes precedence over ordinary version-only resume.
• incomplete, failed, and stale describe attempt lifecycle states, not additional submission grades. None earns a badge.

Rules

• User-invoked on purpose: starting a graded exercise is the learner's deliberate choice.
• Grade submissions and record attempts; never perform the exercise for the learner, write their artifact or account, or roleplay their actions as learning evidence. Leave user-only actions for the human to invoke.
• Keep L2 even when a pipeline exists: a frozen execution order does not demonstrate the learner's reasoning about order, omission, and authority.
• Advance the exercise; leave catalog orientation and routing elsewhere. No guide installation is required. Do not turn the lesson into an execution pipeline or a general workflow recommender.
• Claim no competence, certification, ranking, or measured learning effect. Human transfer requires a human applying the skill to a new task and remains unmeasured by this tutorial.

Verification

Check these seven disjoint scenarios against the rules before finishing. Resume cases determine lifecycle handling before submission grading; they are not substitutes for a submission grade. Each row has one outcome and one record action.

Confirm every record uses an unused path, includes the required fields, and leaves earlier records intact. Report the actual grading or resume result without claiming a human completed or transferred learning during validation.