aipuria Times
Everything a first-time faculty needs — the game's inner mechanics and the platform's working, in plain language.
This handbook exposes the game mechanics, scoring internals, AI-judge logic and anti-cheat design. Sharing it — even a screenshot or the PDF — lets students game the rubric and destroys the assessment's integrity. If a student asks for "the docs", send them the Student Playbook at /student-guide instead. Never forward, paste, print, screenshot or upload any part of this page (or its PDF) to a student-visible channel.
Propaganda Wars is a browser-based, single-player media-literacy simulation. The student steps into the role of the incoming editor of a fictional newspaper — The Jaipuria Times — that is being out-published by a rival broadsheet, The Daily Contrarian. Over three editions (rounds), the rival releases an article laced with well-known propaganda techniques. The student must:
One full session lasts 15–25 minutes. Students may play unlimited sessions, but only the last 3 sessions are considered for the grade — the highest score among those three is what the faculty sees. Extra plays beyond three push older attempts out of the counted window.
These are the eight classical techniques the rival paper draws from. Students must spot which are present in each article.
Each round produces four sub-signals that combine into the round's score, then all three rounds combine into the final rubric.
| Signal | Earns marks when… | Loses marks when… |
|---|---|---|
| Detection | Correct techniques ticked, no false positives. | Missed techniques, or ticked techniques not present. |
| Editorial quality | Coherent argument, addresses the rival's specific claims, uses evidence or reasoning. | Off-topic, generic, or gibberish. Auto-capped at 0 by the gibberish floor. |
| Sentiment shift | Combined detection + writing moves the public meter toward truth. | Weak or empty answers move it toward the rival. |
| Depth of engagement | Multiple rounds show iteration, reflection, and critical use of the tools. | All three rounds feel identical or perfunctory. |
The rubric is holistic — it grades the whole session, not each round separately.
| Component | Marks | What we look for |
|---|---|---|
| Depth of Engagement | / 5 | Iterations, prompts, reflection, critical use of AI across the three rounds. Did the student probe or just click through? |
| Clarity & Insight | / 5 | Framing of the problem, quality of arguments, awareness of pros & cons, essay-readiness of the counter-editorials. |
| Total | / 10 | Bands: Exceeds (≥ 70%, 4–5) · Meets (35–70%, 2–3) · Below (< 35%, 0–1). |
Aggregation: the dashboard ranks students by the highest rubric_total among their LAST 3 sessions. If a student plays more than three, older attempts drop out of the counted window (they remain visible when drilling into the student but do not affect the headline grade).
Written for readers who have never seen the codebase — the key ideas only.
game_runs table.rubric_total among the student's 3 most recent sessions. Older attempts stay in the database for audit but do not affect the headline score.Three layers of intelligence sit behind the scoring — treat them as indicative, not infallible:
Anti-cheat surface (deterrent, not fortress):
| In-game Title | Who | Sees |
|---|---|---|
| Group Editorial Director | Dr. Shiva Kakkar | All campuses, all faculty, all students, full admin doc, campus summary. |
| Consulting Editor — Tech | Gourab Chatterjee | Same as above (admin). |
| Editor-in-Chief | Dr. Daneshwar Sharma, Dr. Kajal Srivastava, Dr. Radhika Bansal, Dr. Ghanshyam Pandey | All teacher views + Campus Summary. |
| Managing Editor | All other faculty mentors | Only students who registered under their own faculty mentorship. |
| Reporter | Every student account | Only their own play sessions and history. |
STUDENT_ACCESS_CODE shared with the class, TEACHER_ACCESS_CODE with mentors, ADMIN_ACCESS_CODE with the Editorial Director / Consulting Editor. Ask Shiva or Gourab for the current values.The generator and the AI judge both operate under a hard content policy. Rival articles will never reference party politics, religion, communal/caste identity, or live public controversies (Kashmir, Palestine/Israel, Ukraine, sectarian violence, sexuality/gender-identity debates), and real politicians / religious institutions are never named. If a generated article ever drifts, the platform auto-scrubs it and serves a neutral choice-aware fallback.
The same policy is applied to student submissions. Rubric scores are unchanged (we grade the essay-planning craft, not the topic), but any editorial that veers into party politics, religion, or communal territory receives a ⚠ Policy note in the feedback. Faculty see the same note attached to the student's row in the dashboard. Use it to redirect students back to their SDG + industry brief.
Check spam. If missing, sign up again with the same email — Supabase resends the confirmation. If still missing, an admin can mark them confirmed manually.
Only an admin (Shiva or Gourab) can correct the profile. The student must NOT create a duplicate account — roll number and email are unique.
Students reset their own via the 'Forgot password' link. A reset email is sent only if the address is already registered.
By design. Managing Editors see only their mentees. Editors-in-Chief and above see across faculties.
Yes. Open the session report and read the editor's notes and editorials verbatim. Your judgement is final; the AI score is a starting point.
Unlimited sessions. The grade is the best of their LAST 3 completed sessions — extra plays beyond three drop the oldest attempts out of scoring. A stronger fresh session always helps if it beats one of the current counted three.
No. Treat it as a discussion prompt. Ask the student to walk you through their reasoning; if they can, override the flag.
A heuristic gibberish floor caps that round at 0 before the AI ever grades it, so it can't inflate the score.
They email ailabs@jaipuria.ac.in and CC their faculty + gourab.chatterjee@jaipuria.ac.in with the mandatory subject format.