Students

The classroom introduces the tools. The student keeps them.

Participating students receive PrometheOS free for personal and educational use so they can continue learning without the school buying a separate computer for every student.

Explore What Students Build See the Learning Path
Student invention moving from a question through a working prototype to documented evidence
The project can leave the classroom as files, documentation, and a method the student understands.

Classroom-to-home continuity

Keep the project moving after the bell.

PrometheOS gives students a practical way to carry classroom work into personal and educational experimentation with compatible equipment.

  1. 01

    In the classroom

    Build on the shared lab

    Work with the classroom hub, team station, shared equipment, guided projects, and instructor support.

  2. 02

    Carry it forward

    Export the project

    Keep project configuration and documentation together so the work can be imported and continued.

  3. 03

    At home

    Reconnect with compatible equipment

    Install PrometheOS on compatible equipment, connect an affordable ESP32, import the project, and keep experimenting.

  4. 04

    Over time

    Build a body of evidence

    Preserve diagrams, logs, tests, decisions, and revisions as a portfolio of real technical growth.

Compact ESP32 workbench with an input, sensor, output, and local PrometheOS connection
A home setup can be smaller than the classroom lab while preserving the same system ideas.

A compatible home workbench

Continue the method without recreating the entire classroom.

Home continuation uses compatible personal equipment; it does not imply that classroom hardware goes home with each student. An affordable ESP32 and appropriate low-voltage components can provide a focused place to reconnect and experiment.

  • Import classroom project work into a personal installation.
  • Reconnect a smaller set of safe inputs, sensors, and outputs.
  • Change one part of the behavior and document what happens.
  • Export the next version so the work remains portable.

Personal projects still require appropriate supervision, safe wiring, correct power supplies, and responsible testing.

Portfolio evidence

Show the thinking behind the working system.

The strongest evidence is not only that the device worked once. It is a traceable record of what the student built, tested, learned, and changed.

  • Diagram How components and systems connect
  • Configuration The state, rules, and permissions chosen
  • Test Expected behavior and observed results
  • Failure case What broke or behaved unexpectedly
  • Revision What changed and why
  • Reflection What the next version still needs

Technical growth

Let project needs pull students deeper.

Students can begin with configuration and visible cause and effect, then move into the technical layer that helps the next idea work.

  1. StartInputs, outputs, and visible automation
  2. ConnectElectronics, sensors, and ESP32 systems
  3. CoordinateNetworking, distributed state, and diagnostics
  4. ExtendLinux, Python, APIs, and databases
  5. SpecializeFirmware, perception, interfaces, and original systems

Keep exploring

Start with a project. Follow the system wherever it leads.

Project gallery Find an input, behavior, or problem worth building around. Curriculum path See how wiring, logic, networks, interaction, and capstones connect. Safety guidance Keep low-voltage work supervised, protected, and responsible.