Living Word Cooperative "Shared Scene Quest" (Phase D-7)
STATUS: DRAFT. The distribution wedge's cooperative heart: a class shares ONE goal that no individual can finish alone — mapping onto the body-of-Christ / different-gifts theme. No individual ranking (AI-Bridge + R3 ethos). Overlaps the live-play spec (D-4); the async-shared-goal mechanic is the shared foundation.
§1 — Purpose
A teacher sets a class quest (e.g. "Recover all 7 Creation scrolls — each student finds one"); students' individual contributions roll up to a shared class total; the class "wins" together. Plan steer: start with async shared goals (poll a shared counter) — 80% of the value, ~10% of realtime cost.
§2 — What exists / what's needed
- Have: classrooms, anonymous students,
lw_classroom_student_activity(completion events — already a per-device contribution signal), aggregate report. - Need: a "quest" definition (goal + target + how a contribution counts), per-class progress aggregation (largely reuses activity data), and an in-game surface that tells the student "your class needs X more — go find one."
§3 — Decisions (founder)
| # | Decision | Notes |
|---|---|---|
| CQ1 | What counts as a contribution | Reuse encounter completions (lw_classroom_student_activity)? Or a bespoke "collectible" per scene (the "scrolls")? |
| CQ2 | Quest catalog | Teacher picks from preset quests per scene, or a generic "complete N encounters as a class" goal? Preset quests = more curriculum work (founder-authored). |
| CQ3 | No-ranking guarantee | Confirm: shared total only, never per-child leaderboards. (Matches reporting R3 + "don't rank kids.") |
| CQ4 | Relationship to live-play (D-4) | Is this a flavor of a live session, or always-on (a class works toward the goal across the week, async)? Recommend always-on async first (no scheduling needed), with live-session framing later. |
§4 — Proposed v1 (pending CQ1–CQ4)
Reuse lw_classroom_student_activity as the contribution signal (CQ1=completions). A lw_classroom_quests row (classroom_id, scene_id, goal_label, target_count, status). In-game: a joined device sees "Your class: 4/7 — complete an encounter to add one." Teacher view: shared progress bar (aggregate). All async-poll; no realtime; no per-child ranking. Bespoke "scrolls" (CQ1=collectibles) is a larger gameplay change — defer unless founder wants it.
§5 — Recommendation
Build on the already-shipped activity data (CQ1=completions, CQ2=generic "N as a class" v1, CQ3=confirmed no-ranking, CQ4=async always-on). This is the smallest of the four remaining items IF it reuses completion activity. Sequence it AFTER live-play (D-4) since they share the async-shared-goal plumbing — or fold a minimal version into D-4.