Hermes Agent
d555071406
Unify beginner syntax while preserving compatibility, repair ownership and parser guards, add verified distribution tooling and VC6 Windows 98 build inputs, and clarify documentation and release status. Preserve DOS build-input line endings and exclude generated binaries/caches.
2.2 KiB
Classroom pilot checklist
Status: ready for supervised learner testing, not classroom certification. Accessibility for learners with learning disabilities is a design goal and is not yet validated by intended learners. Passing tests does not establish it. Use current status for scope, not older feature roadmaps.
Before a session
- Use a build whose platform was actually tested; check
claro --version. On the legacy Windows build the executable isclaro98.exe. - Run
claro testandclaro validatein the extracted project folder. - Prepare a writable practice folder and explain how to stop/close a stuck run.
- Use only reviewed, trusted scripts. Claro is not a sandbox and runs with the learner's permissions; do not collect sensitive information in exercises.
Observe the first hour
- Run hello and change its message.
- Try input, variables and simple arithmetic.
- Introduce one decision, then one small loop, at the learner's pace.
- Follow the ten lessons and first-hour guide.
- Try a small quiz; ask the learner to explain what changed and why.
- Introduce a harmless mistake, run
claro check, and observe whether the message identifies the right line and suggests an understandable repair.
Show one recommended spelling per concept. Do not introduce classes, typing, packages, networking, concurrency or graphics as prerequisites to first programs.
Record feedback
- Can the learner start, run, change and save a program without repeated coaching?
- Which instructions, words, prompts or errors cause confusion?
- Are examples short enough? Is the expected output obvious?
- Can the learner recover from a mistake and understand what a loop does?
- What presentation, pacing or assistive-technology adjustments help this person?
Record observations without claiming one design suits every disability. Get consent before retaining feedback and avoid unnecessary personal/health data. Make one small improvement, then repeat learner testing.
Platform checks, hosted release verification and accessibility feedback are separate milestones. See release status.