M04

Due Date: November 7, 2026

Final integrated Study Buddy: a coherent system with several working workflows, persistent learner adaptation, a polished demonstration, and honest reflection on limits.

Purpose

The final review is a demonstration and a reflection. You show a coherent system that clearly supports your learning, and you explain honestly what it does well, what it does not, and what you would build next.

Honesty about limitations is graded favorably. A clear-eyed account of where your system still falls short is stronger than a demo that hides the gaps.

What to Show

  • An integrated system with several working workflows. Not a pile of disconnected automations; a system whose parts refer to one another.
  • Persistent or semi-persistent learner adaptation. Memory, a learner profile, weakness tracking, or an equivalent mechanism that makes the system behave differently for you over time.
  • A polished demonstration using realistic course use cases. Use actual course materials and situations you genuinely care about.
  • Evidence of analysis, iteration, and reflection. The improvement history from M01 through M04.
  • Honest discussion of limitations and next improvements.

Final Deliverables

  • A working n8n-based Study Buddy system with multiple workflows.
  • A short architecture overview with workflow descriptions.
  • Prompt designs or system-instruction designs for the major agents/workflows.
  • A description of how course materials, memory, and retrieval are handled.
  • An evaluation plan with examples of tests or review criteria.
  • A demonstration showing how the system is used in realistic study situations.
  • A brief reflection describing what improved over time and what still remains limited.

Minimum Final Standard

Your final system should include at least:

  • Three to five meaningful workflows.
  • One document/materials workflow.
  • One conversation workflow.
  • One evaluation or critique workflow.
  • One personalization, memory, or learner-model feature.
  • One realistic demonstration with several use cases.

Expected Outcome

A coherent final system that clearly supports your learning.

How This Review Is Evaluated

Final quality, coherence, demonstration, evidence of learning value, and analysis of strengths and limitations. This review contributes 45% of your project grade, and the full grading rubric applies.

Against the capability checklist, you should be at: architecture finalized; chat workflow and materials ingestion polished; retrieval and memory integrated; a coherent workflow portfolio; learning behaviors integrated and adaptive; evaluation used in your final analysis; a final polished demo; and strong reflective analysis.

Submission Guidelines

(The details for submitting this milestone have not been posted, yet. Please check back.)