Product case study · Pilot-stage prototype
Process Notebook
A learning platform designed to preserve how students worked—their ink, revisions, scratch work, pauses, and AI-help interactions—not only the final answer.
Private working repository · Public-safe demo in development
01 · The problem
A final answer hides the process that produced it.
Teachers often receive a static worksheet after the meaningful evidence has disappeared: false starts, scratch work, revisions, tool use, and the moment a student asked for help. Process Notebook treats that history as the primary record.
02 · Product rules
Capture the sequence of work—not only the submitted answer.
Keep AI help visible in the same history a teacher reviews.
Preserve original handwriting when recognition creates converted text.
Do not automatically grade, rank, predict misconduct, or label students.
03 · What exists
- Teacher PDF upload and student worksheet workspace.
- Stylus ink, text, scratch pages, undo/redo, and append-only event history.
- Teacher replay, feedback, reopening, and PDF export workflows.
- Teacher-triggered handwriting recognition and subject-specific templates.
At the latest verified handoff, the repository had ten tagged milestones and 300 automated tests passing. That describes the project state, not a claim that I personally authored every implementation detail.
04 · Validation I owned
I compared student work across the live workspace, teacher replay, screenshots, and exported PDFs; found rendering inconsistencies; and caught a database migration that existed in the repository but had never reached the live environment. Both blocked release until resolved.
05 · Claims I am not making
There is no completed school pilot, teacher adoption, or measured student outcome yet. The project is a working prototype that still needs a public-safe demo, a current README, real-device testing, and a deeper architecture walkthrough before I market it as production-ready.
Other case study
Résumé Forge →