# In-Class Activity Rubric

Daily individual and small-group activities are graded as **20% of the final course grade** (see [syllabus.md](syllabus.md)). The same rubric applies to every in-class activity unless an activity's `instructions.md` says otherwise.

The three project deliverables (Project 1, Project 2, Final Project) are graded against the **Project Rubric** in the syllabus, not this one.

## Rubric

| Component | Weight | What "Excellent" looks like |
| :---- | :---- | :---- |
| **Completion** | 40% | The deliverable exists, is publicly hosted (or trivially runnable), and clearly meets the activity's stated task. Nothing is half-finished or placeholder. |
| **AI-Use Documentation** | 30% | A traceable log of prompts and tool choices is included (`log_deliverable/history.md` or equivalent). You are honest about what the AI did, what you redirected, and what you accepted unchanged. Use of external AI tools (ChatGPT, Claude, image generators, etc.) is disclosed. |
| **Reflection Quality** | 30% | The `vibe-report.md` engages with the activity's specific reflection prompts — not a generic "I learned a lot" recap. You name a tension, surprise, value choice, or limitation you encountered. AI writing is impermissible in the reflection except for grammar checking (per syllabus). |

## Submission Requirements (every activity)

Every in-class activity submission must include:

1. **Hosted link or runnable code** — under `code_deliverable/` or its hosted equivalent.
2. **AI usage log** — under `log_deliverable/`, capturing prompts and tool interactions.
3. **`vibe-report.md`** — the reflection markdown, answering the activity's specific prompts. Use [week1/7_13/vibe-report-template.md](../week1/7_13/vibe-report-template.md) as a starting template if the activity does not provide its own.

## Grading Mechanics

- Each activity is scored out of 100 against the rubric above.
- Activities with no submission receive 0; partial submissions are graded against `Completion` only.
- The 20% bucket is the unweighted average of all activity scores across the three weeks.
- Late submissions: see course late policy.

## Notes for Activity Authors

When writing an `instructions.md` for a new activity, only override the rubric if you have a specific reason (e.g., a paired group activity where AI-use documentation is replaced by group-process notes). Otherwise, point students at this file.