Building a Classroom Control Plane for Teachers and Student PCs
How the teacher dashboard, student PC helper, command history, and live screen view work together in a classroom.
The operating problem
A classroom operator needs more than a dashboard. They need a dependable control loop across machines that may reboot, disconnect, or receive policy changes at awkward times.
The project separates the browser-facing admin surface from a Rust Windows agent so each side can own the work it is best suited to perform.
Designing for receipts, not hope
Every deployment and command path is designed around observable state. USB launches, install verification, queue progress, and screen readiness produce evidence the operator can inspect.
- A dependency-free Node.js admin console keeps local setup predictable.
- The Rust agent owns Windows service behavior and native capture paths.
- Runtime secrets, machine lists, screenshots, and compiled binaries stay outside Git.
What makes it portfolio-safe
The repository preserves architecture and verification logic while excluding real classroom state. That distinction matters: a useful portfolio explains the system without publishing operational data.