Skip to main content

Movement 1 — From Spark to Stakes

Why RTS?​

Too often, I've seen undergraduate multimedia projects stall at the threshold of production. Students arrive with research in hand but then feel adrift when asked to translate it into media. "Why am I learning this software if my ideas are already clear?" The question seems practical, but it points to something more: a lingering belief that media production is just a delivery mechanism, and not a generative thinking space. That the work of the story is already finished, and the medium is framed as purely incidental, or worse, “just a tool.”

Many students begin their projects with a quiet dread: the sense that now comes the part they're "not good at." The shift from research to media-making is often framed as a handoff — from thinking to doing, from analysis to decoration. "Creativity" gets cast as an intuitive gift some students have, while communication tools are treated as neutral containers. The result is disorientation, detachment, and a fair dose of missed opportunity.

Research To Story (RTS) begins from a different belief: that making is a way of knowing. That the tools, formats, and rhythms of media production don't just convey ideas, they have the power to reshape them. RTS is designed to help students notice their thinking evolve as they build and to experience making as more than some "techie" interruption, but as another place where their questions stretch, clarify, and come alive.

It's really about recovering the spark that made the topic matter in the first place and discovering what that spark can become when it meets a medium, an audience, and their own voice.

For the full project introduction and feature overview, see Introduction.

Movement 1: The Generative Engine of the Entire RTS Framework​

While students work on the "aboutness" of their research topic, Movement 1 is designed to present another layer — intervening to help the student elaborate on that topic by weaving early curiosity, identity, and audience awareness into a threadable narrative posture. Pedagogically, this is the groundwork for going from research to story.

In the RTS system, Movement 1 serves as a type of incubation chamber for topic development — for a topic that is not going to live in a research paper but rather a podcast or audio essay. While it does function somewhat like a brainstorming tool, it is a deliberate pedagogical structure that aims to cultivate a reflective stance on the inquiry process through three foundational postures:

  • 🧭 Personal Connection
  • 🔬 Research Potential
  • 🎯 Audience Awareness

These postures frame the journey of Movement 1 from "Spark to Stakes" and are the rhetorical (and pedagogical) ingredients for this early fusion of thinking and making. Every RTS session begins here, and a purposefully developed Movement 1 sets the thread that carries through any subsequent movements that could be developed.

From a Development Perspective, Movement 1:​

  • Establishes the session_id: the root container for a student's inquiry
  • Seeds reflective traces and metadata for all downstream movements
  • Surfaces student voice, but in structured tension with scholarly framing and public orientation
  • Grounds AI in context-aware follow-up logic, structured around five ideational categories and a recursive synthesis loop

This movement is designed to transition students from "What is my research about?" to "What can my research do out in the world?" — with the podcast medium as the communicative target.

The Three Postures: From Spark to Stakes​

Purpose​

To surface the raw energy and purpose behind a student's interest — before citation, before structure. The work of Movement 1 is to discover what's already alive under the surface.

🔹 1. Personal Connection​

Core Question: What drew you to this topic?

Pedagogical Goal: Uncover students' lived curiosity and experiences.

Outcomes:

  • Articulate a personal stake
  • Identify genuine confusion or curiosity
  • Reframe research as agency

Sample Prompts:

  • What first pulled you toward this topic?
  • Even if it was assigned, where do your experiences or interests meet the subject?
  • What feels unresolved or confusing right now?

🔹 2. Research Potential​

Core Question: What do you want to figure out?

Pedagogical Goal: Highlight contradiction, complexity, and intellectual stakes.

Outcomes:

  • Frame meaningful questions
  • Surface gaps or challenges
  • Identify scholarly friction

Sample Prompts:

  • What assumptions does everyone seem to make?
  • What has surprised you so far?
  • Where have you changed your thinking?

🔹 3. Audience Awareness​

Core Question: Why does this topic matter to others?

Pedagogical Goal: Shift toward rhetorical purpose.

Outcomes:

  • Specify a public or disciplinary audience
  • Clarify intended impact
  • Figure out what "evidence" will look like

Sample Prompts:

  • Who needs to hear this story?
  • How would you explain this to a friend, policymaker, skeptic?

The 4-Round Journey​

Session-Level Structure​

  1. Student enters a topic (messy, personal, or specific)
  2. The system initiates a 4-round journey:
    • Each round includes:
      • AI-generated interpretive summary of the student's work so far
      • 10 follow-up questions (2 per category — see below)
      • Student chooses 1 to answer
      • System logs selected Q&A + unused questions + all AI metadata
    • Each round builds on the previous — generating a reflection trail
  3. At the end of Round 4, the AI generates a synthesis of the student's inquiry arc as a “mentor-style” letter in markdown format.

The Five Ideational Categories​

CategoryGoal
🔥 Spark of InquirySurface personal resonance, formative moments, naive curiosity
📚 Inquiry as StoryFrame scholarly tension as narrative
🌎 Stakes and SignificanceArticulate broader impact and urgency
🧩 Puzzles and UnknownsExplore contradictions, gaps, and uncertainty
🎧 Listeners and LensImagine the rhetorical impact and shape of a podcast episode

These categories guide question generation, reflection logging, and later deep dives. After the core 4 rounds, students may choose to "zoom in" on any category through a Deep Dive — a focused 4-round exploration using category-specific subcategories (e.g., Spark of Inquiry breaks into "The Origin Scene," "The Emotional Core," "The Naive Question," and four more).

For details on how AI generates these questions and syntheses — including the constraint architecture, structured JSON output, and observability metadata — see A Note on AI Use.

Pedagogical Principles at Play​

  • Research is content discovery and story preparation.
  • Reflection is additive and foundational to inquiry.
  • GenAI is positioned as a constrained text processing system — generating questions and reorganizing text, not providing answers. The metaphors we use to describe this process matter and deserve scrutiny.
  • Observability matters — students can review all their AI interactions, token metadata, and intermediate computational artifacts.

The Conceptual Model: Three Anchors​

RTS is built around deep, reflective engagement with a single topic — a session. But this process is always contained within a course. Nothing in RTS happens outside that scope.

course_id — The Walled Garden​

Every RTS journey lives inside a course. A course may have many sessions (different research projects or topics a student explores over time), but these sessions do not exist globally — they only make sense within the context of a course. This allows instructors to assign multiple RTS sequences over time, while keeping data scoped to that course's theme, pacing, and instructor guidance.

session_id — The Inquiry Thread​

A session_id is the anchor for a single, continuous research story.

  • It's equivalent to a notebook, a research journey, or a topic thread.
  • All reflections, AI-generated outputs, metadata, and artifacts (syntheses, deep dives, etc.) are scoped to a single session_id.
  • On a student dashboard, the session is what they "click into" — it's their project.

Example: A student in a course might have two sessions over time — one exploring AI in Education, another exploring Narrative Journalism. Each has its own session_id, even though both live inside the same course_id.

movement_number — The Narrative Timeline​

RTS is sequenced through a scaffolded progression called Movements — each one guiding a different mode of reflection, analysis, or research action.

  • A movement_number marks where a student is in that journey.
  • Movements are ordered (e.g., 1, 2, 3 … 6) and each holds unique prompts, outputs, and pedagogy.
  • All activity in RTS is both session-specific and movement-specific.

The Triple​

Everything in RTS — AI questions, student responses, metadata, synthesis — is scoped to this triple:

{
  course_id: UUID,              // the learning container
  session_id: UUID,             // the project container
  movement_number: integer      // the stage of inquiry
}

In database terms: session_id + movement_number determines which reflections, AI prompts, syntheses, and metadata are relevant.

How This Enables the RTS Dashboard & Ledger​

This structure allows for flexible yet organized views:

  • Dashboard view: "Show me all my sessions across time, sorted by course."
  • Session view: "Show me my full narrative journey for this topic, across all Movements."
  • Ledger view: "Audit all the AI-generated outputs, student reflections, and narrative artifacts tied to a given session."

RTS never functions without all three of these anchors. For the complete database schema and table definitions, see Database & Living Ledger.

Developer Quick Reference​

Query Pattern: Full Narrative Trace with AI Metadata​

To retrieve a complete Movement 1 journey for a single session — reflections, questions, synthesis, and all observability data:

SELECT
  r.round_number,
  r.user_reflection,
  r.interpretive_summary,
  f.category,
  f.question_text,
  m.synthesis_text,
  r.prompt_token_count,
  r.response_token_count,
  r.thinking_token_count,
  r.total_token_count,
  r.thought_summary,
  r.model_used
FROM reflection_rounds r
JOIN followup_questions_log f
  ON r.answered_question_id = f.id
LEFT JOIN movement_synthesis m
  ON r.session_id = m.session_id
  AND m.movement_number = 1
WHERE r.session_id = '<session-uuid>'
  AND r.movement_number = 1
ORDER BY r.round_number ASC;

For table schemas, column definitions, and Row Level Security policies, see Database & Living Ledger. For the handler trio pattern (generate → save → synthesize) and how AI interactions are constrained, see A Note on AI Use.

Movement 1 is where the process begins...with a spark. The work here is to find what's alive in a student's curiosity and to discover what that spark can become when it meets a medium, an audience, and their own voice.