Curated assignment assistant commons

# Curated assignment assistant commons

A controlled path for trusted teachers to create custom assignment types, tutors, and grading assistants without letting every teacher mutate Yawp's canonical tutor/grader behavior.

## Source

Granola meeting: `3fbd5f2d-e409-42bd-b585-fed305edd5cd`, **Summer priorities — assignment types, LMS integration, and reporter**, 2026-05-26 1:31 PM CDT.

The team leaned away from open teacher control over tutor/grading assistant prompts. The preferred direction was a curated/certified teacher sandbox: selected teachers can create over "over here," Yawp reviews quality, then the best work can be published for broader reuse.

## Problem

Yawp's value is partly that the tutor and grading assistant reflect strong domain expertise and a consistent instructional personality. If every teacher can freely edit the tutor/grader prompts, product quality can collapse quickly.

But there is still real upside in letting excellent teachers contribute:

- New assignment types.
- Subject-specific rubrics.
- Course-specific tutoring flows.
- Reusable classroom-tested materials.

## Goals

- Let selected/certified teachers experiment with custom assignment assistants.
- Keep canonical assignment types immutable for normal teachers.
- Require Yawp approval before custom work is published widely.
- Preserve provenance: who created it, who reviewed it, what changed.
- Build toward a Yawp-approved commons/library of high-quality teacher-created materials.

## Non-goals

- Giving every teacher a blank prompt box.
- Letting custom work alter core Five Paragraph, Thesis Driven, or Daily Pages behavior.
- Shipping this before canonical assignment-type expansion stabilizes.
- Letting unreviewed custom graders affect production grades for broad users.

## UX sketch

Certified creator flow:

```text
Create custom assistant
  Assignment type name
  Student task
  Tutor goals
  Grading dimensions
  Example submissions / expected feedback
  Save draft
  Submit for Yawp review
```

Admin/Yawp review:

```text
Review custom assistant
  Test with calibration examples
  Approve for pilot
  Publish to organization / publish to commons / reject
```

Normal teacher:

```text
Assignment type picker
  Yawp approved
  School approved
  Created by certified teachers
```

## Open questions

- [ ] Who counts as a certified creator in v1: Kevin/Brian only, selected pilot teachers, or school admins?
- [ ] What review gate is required before a custom grading assistant can produce grades?
- [ ] Is this named as "Yawp Commons", "Yawp Collective", or just "Approved assignment types"?
- [ ] Can custom assistants be copied and modified, or only used as-is?
- [ ] Does a school own its custom assistants, or does Yawp?

## Test plan

- E2E: unauthorized teacher cannot create custom assistant.
- E2E: certified teacher creates draft custom assistant.
- E2E: custom assistant cannot alter canonical assignment types.
- E2E: admin approves custom assistant for pilot use.
- Unit: assignment type resolution never lets unapproved custom assistant replace canonical tutor/grader.

## Rollout

1. Internal-only with Kevin/Brian.
2. One certified pilot teacher.
3. Organization-approved custom assignment types.
4. Broader Yawp-approved commons.

## Engineering handoff checklist

- [ ] Domain context covered
- [ ] File paths in `yawp-2.0` listed
- [ ] Data model implications spelled out, including backward-compat plan
- [ ] UX sketch in prose
- [ ] Edge cases enumerated
- [ ] Test plan written
- [ ] Rollout plan decided