Product walkthrough

How Atelo builds a course for one person.

A look at the real product, feature by feature — the placement that finds your level, the course built around it, the lessons you actually run, and the proof you leave with.

  1. 01Placement
  2. 02Generation
  3. 03Lessons
  4. 04Challenge
  5. 05Archaeology
  6. 06Capstone
  7. 07Proof
01 · Adaptive placement

It finds your real level first.

A short adaptive test adjusts to each answer and stops once your level is clear. The result is a skill profile, not a score. Sample learner below: solid on syntax, shaky on predicting what code does.

Sample placement: 11 answers — syntax solid, three of four runtime-prediction questions missed.

02 · Course generation

Then it builds the course around that.

A full course — modules, a capstone, skill tracking — built around your level, goal, and project, and checked before you ever see it. Here's a real one.

A generated Atelo course: module map, continue-learning panel, skill tracking, and capstone readiness.
03 · Lessons

Lessons you run, not just read.

Every lesson is predict-run-repair on a live runtime: predict the output, run the real code, fix what you got wrong. Inline quizzes, a short warm-up drill, and Ada — who gives hints, never the answer. A concept you miss comes back in a later lesson.

An Atelo lesson: concept text with a drop cap, the lesson spine rail, a saved goal, and an interactive predict-before-you-run block.

Not a screenshot — predict the output and run it yourself:

live python · runs on a real runtime
Predict the output
04 · Module challenge

Each module ends in a build.

Write a plan first, then real code against visible and hidden tests. Ada has your challenge, plan, and tests as context and gives hints only — never the final answer. The module gate opens once every test passes.

An Atelo module challenge: brief, code editor with real Python, visible and hidden tests, plan-before-tests panel, and the Ada tutor.
05 · Code archaeology

Read real production code.

After a module, walk real project code line by line and name the patterns you just learned — control flow, state, error paths. Recognising a concept in code you didn't write is what makes it stick.

Atelo code archaeology: real project code read line by line, with annotations naming the concept each line uses and a continue action.
06 · Capstone

Your work becomes one project.

The code you wrote across modules assembles into a capstone that runs on the same real runtime — then you record one architectural decision in your own words. Real assembled work, not a quiz score.

An Atelo capstone: the learner's assembled module files in a code editor, a real runtime terminal, and an architecture-reflection prompt.
07 · Proof

It ends with proof you can verify.

A proof page recomputed server-side from your recorded work and signed, so it can't be faked from a URL. At publish, your capstone re-runs on fresh data it never saw — a hardcoded answer fails. Then it's a link you can share.

An Atelo proof page: verified course-completion banner, proof score, capstone evidence, and a shareable verification link.
In short

One course, built for one person — and proven on real code.

Adaptive placement, a course generated and validated around the gap it finds, predict-run-repair lessons on real code, and proof that re-runs server-side. Early access — every course is $15, built for you, yours to keep.

  1. 01Placement
  2. 02Generation
  3. 03Lessons
  4. 04Challenge
  5. 05Archaeology
  6. 06Capstone
  7. 07Proof