What this is

qed’bop pairs public-domain poems with musical settings and turns the pairing into a discussion lesson you can share with students by URL. Pick a poem, pick a recording of it, get three to five AI-generated discussion questions calibrated to your students’ level, share the link. No accounts. No tracking. Students click the link, hear the music, read the poem, answer the questions.

Why music

A poem is one thing on the page and another thing in a singer’s mouth. Asking students to compare a text with one of its musical settings forces interpretive work that silent reading rarely does on its own — what does the arrangement emphasize, what does it strip away, what does it argue about the poem that the words alone don’t say. That comparative work is the lesson.

The AI-resistance moat

Discussion questions on qed’bop are deliberately general about the music: “identify a moment where the instrumentation changes unexpectedly and explain its interpretive effect.” They never name a timestamp or a specific musical event. Students have to supply the specificity from their own listening, which general-purpose chatbots can’t fake without actually hearing the recording.

Every assignment includes at least one “find and describe” question that requires identifying a specific moment in the music, describing what was heard, and explaining its interpretive effect. That requirement is structural — it’s the proof of engagement.

Privacy

Students don’t sign in. There’s no account, no email, no analytics on individual learners. The student page contains the poem, the videos, and the questions — nothing else. Assignment state lives entirely in the URL, which means sharing a lesson is just sharing a link.

State of the project

qed’bop is intentionally a small, focused tool. The catalog is hand-curated and grows slowly. Features only ship when they earn their keep against the core loop. If something looks rough, it’s probably because the next version of it is more important than polishing the current one.