Week 8: Project Proposal Presentation (Midterm Replacement)

Midterm EvaluationWeek 8Midterm ReplacementLecture: 2026-04-21

Small class → Individual projects

Reflecting the small class size, the capstone runs as individual projects, not team projects. The Week 8 midterm is replaced by individual project proposal presentations instead of a written exam.

Week 8 Overview

Week 8 falls on the midterm exam period. Instead of a written exam, students write and present their individual capstone project proposals. The goal is to connect the concepts from Weeks 1–7 (HOTL, MCP, Ralph Loop, Context Rot, instruction tuning, multi-agent SDLC) into a concrete project design.

Midterm project weight: 20% of the final grade

---

How to Submit

Submission Location

Submit via GitHub PR at:

capstone/projects/[student-id]/proposal.md

Example: capstone/projects/20230001/proposal.md

Submission Steps

1. Fork the repo and create a branch

   git clone <course-repo>
   cd <course-repo>
   git checkout -b proposal/20230001

2. Create the directory and write the proposal

   mkdir -p capstone/projects/20230001
   # Write proposal.md (see template in the guide below)

3. Verify the build

   pnpm install --frozen-lockfile
   pnpm run build

   Do not submit a PR if the build fails.

4. Open the PR

   • PR title: [Proposal] Capstone - 20230001 Hong Gildong
   • Base: main / Compare: proposal/20230001
   • Include a one-line project summary in the body.

5. Register your project

   Also add your entry on the project registration page.

Deadlines

• Proposal PR deadline: 2026-04-20 23:59 (the day before Week 8 class)
• Presentation: 2026-04-21 (during class)
• Final approval: Incorporate instructor feedback and revise by 2026-04-28

---

Proposal Writing Guide

To keep proposals consistent and specific, all students follow the same template. The detailed guide and template:

Proposal Writing Guide

Standard template + writing principles + examples

→ /en/capstone/proposal-guide

Project Registration

Register your project before submitting the proposal

→ /en/capstone/teams

Required Sections

Every proposal must include all 8 sections:

1. Problem Definition — Current state, why agentic approach is needed
2. Proposed System Design — Agent roster, pipeline architecture, MCP tools
3. Tech Stack — Model, framework, language, deployment
4. Course Technique Mapping — Which Week 1–7 techniques you will use and how
5. Development Schedule — Milestones for Weeks 13–16
6. Success Criteria — Quantitative metrics
7. Risks and Mitigations — Expected risks and mitigation strategies
8. References

The most important sections

§2 (System Design) and §4 (Course Technique Mapping) account for half of the grading points. Include at least one diagram and a week-by-week technique mapping table.

---

Presentation Schedule

Each student: 15 min talk + 5 min Q&A + 5 min instructor feedback = 25 min. Slot count adjusts to the number of enrolled students.

Example schedule:

Time	Slot	Notes
09:00–09:25	#1	Start
09:25–09:50	#2
09:50–10:15	#3
10:15–10:30	Break
10:30–10:55	#4
10:55–11:20	#5
…	…	Extend for additional students
Last 20 min	Wrap-up & peer evaluation

Order: Assigned by the merge time of each student’s proposal PR (first to submit presents first).

---

Grading Rubric

Criterion	Points	Description
Clarity of problem definition	4	Why this problem, why an agentic approach
Specificity of system design	6	Agent roster, artifacts, pipeline
Application of course techniques	4	Explicit links to Weeks 1–7
Feasibility	3	Achievable in Weeks 13–16
Presentation quality	3	Clear delivery, Q&A responsiveness
Total	20	20% of final grade

---

Practicum

Goals for today

Present your own project and exchange peer feedback while listening to others’ plans. Incorporate instructor feedback to finalize your proposal.

1. Prepare slides (before class)

   Prepare a 15-minute deck. See the presentation structure in the proposal guide.

2. Present (during class)

   Focus on diagrams when explaining system design. Always show the course technique mapping table.

3. Peer feedback

   Submit at least 2 constructive questions/suggestions for each other student’s presentation. Evaluation form distributed in class.

4. Incorporate feedback (after class)

   Apply instructor feedback to your proposal. Push the revised proposal.md to the same PR.

5. Final approval

   Finalize the plan by 2026-04-28. Implementation begins in Week 13.

---

Assignment

Capstone Project Proposal

PR deadline: 2026-04-20 23:59 Presentation: 2026-04-21 (Week 8 class) Final revision deadline: 2026-04-28 (after feedback)

Requirements:

1. Write capstone/projects/[student-id]/proposal.md following the template
2. Include all 8 required sections
3. At least one pipeline diagram
4. Course technique mapping table (link at least 5 weeks)
5. Quantitative success criteria (at least 3 metrics)
6. Add your entry to the project registration page
7. PR must pass pnpm run build

After submission:

• Prepare a 15-minute deck
• Present in class + peer feedback
• Final revision by 2026-04-28

---

Key Summary

1. Week 8 replaces the exam with a proposal presentation — evaluates your ability to translate concepts into design, not memorization
2. Individual projects — 7-student class runs as individuals, not teams
3. Standard template — ensures consistency and fair evaluation. See the Proposal Writing Guide
4. Specific > general — “Automatic code fixes from pytest failures” instead of “AI improves code”
5. Technique mapping required — explicitly link to at least 5 of Weeks 1–7
6. Submission path: capstone/projects/[student-id]/proposal.md (GitHub PR)

Further Reading

• Project Proposal Writing Guide — Template and writing principles
• Capstone Overview — Schedule and grading
• Project Registration — Register your project
• Detailed Rubric — Full capstone rubric