# Claro Learning-First Development Charter

Claro is a learning tool first and a general-purpose programming language second. Prioritize an easy first experience, especially for learners with learning disabilities, without assuming one design suits every learner or claiming accessibility validation without learner testing.

## Active priorities

- Keep syntax, rules, and behavior simple, predictable, and consistent.
- Favor the small core: `SAY`/`ASK`, variables, basic arithmetic, decisions, loops, lists, simple functions, and text-file save/load.
- Teach one recommended syntax per concept. Keep supported compatibility forms working, but outside the initial learning path.
- Teach one concept at a time with short explanations, runnable examples, small exercises, visible results, and concrete expected output.
- Make errors identify the line, explain the problem without blame, and show a repair.
- Fix broken examples, inconsistent core behavior, and simple-core crashes before considering features.
- Do not pursue advanced type systems, concurrency, package registries, web frameworks, complex object models, or graphics systems absent an explicit request.
- Claro runs trusted scripts; it is not a sandbox.

Older roadmap documents preserve project history and describe prior ambitions. This charter guides current work without removing supported features or erasing that history.