Praxis pilot.

Two different percussion apps. One skill profile — and an honest line between what a browser measured and what still needs a teacher.

This is the first working slice of Praxis, not the finished product. It runs entirely in this browser: no account, no sign-in, nothing uploaded.

What this demonstrates

  1. 1
    Count It asks what you knowthe pattern's name, its spelling, how it's built.
  2. 2
    Copy the Sticking turns two keys (or two on-screen pads) into a controller and checks whether you can enter the pattern from memory.
  3. 3
    One combined profile holds both results — kept as separate kinds of evidence, never averaged into a single misleading number.
  4. 4
    The pilot tells you what to do next — retry, practise, or join the pass-off queue — from fixed rules, not a guess.
  5. 5
    A teacher verifies the playing — grip, rebound, tone, pulse, musical execution. The part no browser can judge.
Read this before you start. This pilot is deliberately careful about what it claims. A perfect score here means you answered correctly and pressed the right triggers in the right order. It does not mean you played the rudiment well — that judgement stays with your teacher.

What it measures

  • Answer correctness
  • Recall of the R/L pattern
  • Which triggers were pressed, in what order
  • Missed strokes, extra strokes, first error

What it cannot measure

  • Which physical hand you used
  • Grip, rebound, stroke quality
  • Tone, sound, dynamics
  • Rhythm and timing (not in v0.1)

Start here

or open one activity directly
for teachers

Before you try it in a classroom

Nothing is uploaded, and there are no accounts
Every result stays in this browser's local storage on this device. There is no server, no sign-in, and no student name, email, school ID, or date of birth anywhere in the system. Nothing is recorded through a microphone or camera.
Sharing a device? Use a learner code
On a shared Chromebook or lab computer, each student picks a short learner code (like P03) in the bar at the top of the pilot home. Results are stored separately per code, so students on the same device don't see or overwrite each other's evidence. The code is a pseudonym — it is not a name, and it is not tied to any identity.
Clearing browser data resets the demo
Because everything lives in local storage, clearing site data — or a device that wipes profiles between sessions — resets progress. The pilot will not pretend earlier mastery survived. Students can copy or print a result receipt after any attempt if they need a record that outlives the browser.
What's deliberately not here yet
No accounts, no backend, no class rosters, no gradebook sync, no microphone grading, and only three skills — single stroke roll, double stroke roll, and single paradiddle. This slice exists to test whether the cross-app evidence loop actually helps a teacher decide what a student should do next. Everything else waits on that answer.