How to find the students who are struggling for the right reasons — and can improve fastest with the right help
Imagine two students after the first OPPE. Both have low scores. One keeps running tests, edits code thoughtfully, and fails in a repeatable pattern. The other submits once, or keeps making random edits with no clear direction. They look the same on marks. They are not the same learner.
This story is about that difference. We are not asking, “Who scored poorly?” We are asking, “Who is most likely to improve quickly if we intervene now?”
To answer that, we used coding process traces: test-run cadence, edit behavior, error signatures, concept struggle patterns, and persistence markers. The result is a decision tree that isolates a practical intervention set: about 1 in 10 profiles.
The tree has seven leaves. Four are not intervention-priority today (D0, D1, D2, D3). Three are the teachable tracks: T1 syntax foundations, T2 runtime debugging, and T3 logic/edge cases.
Click any node below to open a full breakdown with real student examples, dominant error signatures, and intervention guidance.
The median story: most profiles are stable (D2, 57.2%). But the operational opportunity is in the colored slice. The teachable set is not giant. It is manageable. And it is rich in actionable structure.
Half of the teachable set belongs to one track: runtime debugging. The rest split between logic/edge-case reasoning and syntax structure repair. That matters because each requires different coaching scripts.
Notice the separation in behavior space. D0 is low-run, low-edit. D1 is high-run, high-edit chaos. Teachable tracks occupy the middle-right: enough persistence to work with, but not so much regression that coaching becomes rescue.
Segmentation without pedagogy is just labeling. Each teachable path has a concrete 25-minute intervention recipe in the source report. Click the cards for ready-to-use coaching playbooks.
The recurring concept struggles inside the teachable group are equally actionable. The chart below counts concept mentions in teachable profiles’ top-struggle lists (max 3 per profile). Click any bar to see which path it clusters in and sample student hashes.
The table below is the operational surface: filter by term/path, search student hashes, sort by runs/edits/priority, and click any row for full profile context and recommended intervention track.
| Student | Term | Path | Dominant Error | Avg Runs | Avg Edits | Avg Active Min | Priority Index | Top Concept Struggles |
|---|---|---|---|---|---|---|---|---|
| Loading… | ||||||||
How to read this story: This is a process-first segmentation from OPPE Wave 1 profiles. It is designed for targeted support, not for grading, ranking, or punitive decisions.
Data provenance: computed from analysis/teachable.csv, generated by analysis/teachable.py, documented in analysis/teachable.md.
Related context: REPORT.md, quick-fixes.md, and 2026-02-25-next-steps.md.