learning-loop

The SKUEL learning loop guides feature development by acting as an evaluation lens to ensure new features strengthen the loop's five phases or improve transitions. It determines if a feature aligns with the core purpose or deviates and should be reconsidered.

SKUEL's learning loop defines two tracks, Curriculum and Activity, progressing through five phases. These tracks structure the educational flow, ensuring features enhance the progression through the loop rather than disrupt its fundamental pedagogical philosophy.

Graph relationships in the learning loop connect core entities like Ku, Exercise, Submission, Report, and RevisedExercise. These inter-relationships map the data model, linking associated services to ensure the loop's operational continuity across phases.

The Submission entity represents a critical phase within the learning loop, bridging exercises and reports. Evaluating features against the Submission phase ensures they strengthen student data capture and improve transitions to the subsequent report phase.

Evaluate new features against the learning loop phases during the design stage. This ensures the feature actively strengthens a specific phase, like Submissions or Reports, or improves phase transitions, preventing scope drift from the app's core purpose.

Yes, the learning loop data model includes the RevisedExercise entity. This tracks updates following the Report phase, maintaining the loop's continuity by feeding revised activities back into the curriculum and activity tracks.