AI Partners available for today's work
Remember: every AI use gets documented. → AI Documentation Template

What today is about

Two big moves today. The signature U5 partner lands.

First move: stakeholder analysis basics. The 6-field framework (Who They Are / What They Want / Evidence They Cite / Position / Power / Allies+Opponents) is how you map a real water dispute. The key insight: real stakeholders don't argue from the same evidence; they cite different evidence because their interests differ. Stakeholder mapping is interest-first, evidence-second. A Tamil Nadu delta farmer and a Karnataka upstream farmer don't agree on what the rainfall data means because they don't have the same interest in what the data should imply.

Second move: The Stakeholder Voice AI partner is introduced. The signature U5 partner. It role-plays the strongest version of any stakeholder you name. Making the strongest counter-argument is the move: students rehearse responding to well-formed positions, not to caricatures. The trial-arm split lands today: each section starts a slightly different scaffold (see Interact card below). All three sections are working on the same skill: perspective-taking, the year's T/T centerpiece.

Counter-argument work runs through the whole block. By exit: you've stated the strongest counter to your stakeholder's position fairly, then responded without strawmanning. This is the move the Position Paper's "Acknowledge competing concerns" section needs.

Before you start the work

Start with the Interact: your section arm starts here. The Watch and the Read set it up.

Placeholder
Watch (~6 min)
TBD: stakeholder analysis basics. The 6-field framework demonstrated on one fully-mapped Cauvery stakeholder (suggested: a Karnataka upstream farmer, non-default for many AISC students). Interest → evidence → position → power → alliances.
Read (~5 min)
The Stakeholder Voice AI partner page: what it does, what it won't do, how the failure modes look. Read this before you fire up your section's scaffold.
Placeholder
Interact: your arm starts here (~25 min)
Section A (BoodleBox): Open the Boodle Build Assignment. Begin constructing your custom Stakeholder Voice bot: 8-section system prompt (role + background + beliefs + strongest argument + non-negotiable + honest admission + opponent-framing + cited evidence + constraints). Peer test in Block 8.

Section B (Flint): First Flint Stakeholder Voice session. Ms. Jayanthi/Mr. Ignash configured your stakeholder's persona; you start the conversation, push for the strongest version of the position.

Section C (paper): Open the Stakeholder Profile Pack. Read your chosen stakeholder's 7-section Q&A profile carefully. Annotate what surprises you + what feels familiar.

Today's work: choose one path

All four paths end with one stakeholder-map row (6 fields, fully filled) + one counter-argument paragraph + a 2-sentence response without strawmanning.

Learning Intention: I have identified the strongest counter to my stakeholder's position, written a paragraph stating it fairly, and written my response without strawmanning the counter.
A
Counter-argument + Stakeholder Voice rehearsal (default, all arms)
Identify the strongest counter to your stakeholder's position. Write a paragraph stating it fairly, using the language and evidence that opposing stakeholder would use. Then rehearse with your section's Stakeholder Voice scaffold (your Boodle, the Flint tutor, or a partner reading from the paper Profile Pack). Write your 2-sentence response without strawmanning.
Solo · Default
B
Boodle Build progress (stretch, Section A only)
If you're in Section A and you got an early start on your Boodle, push it further today: run the 5 test questions from the assignment, iterate the system prompt at least twice, document each iteration cycle. Aim to bring a Boodle that sounds like your stakeholder (not generic) to Block 8's peer test.
Solo · Stretch · Section A
C
Counter-argument with OPVL deepening (choice)
Same as Path A, plus OPVL the strongest counter-source (a piece of evidence the opposing stakeholder cites). The Source Evaluator walks the four letters. Specificity on the counter-source's Limitation strengthens your response paragraph significantly.
Solo · Choice
D
Stakeholder mapping peer-help (practice)
If the 6-field framework is fuzzy, come to the peer-help table. Fill in your first map row together with a peer + Ms. Jayanthi/Mr. Ignash. The Murray-Darling worked example brief is the reference; it shows what specific (not generic) stakeholder analysis looks like.
Pairs · Practice

Open your Class Notebook and type today's entry header as Heading 2:

A: Mar 19 | U5 B7 | Stakeholder Analysis + Stakeholder Voice AI IntroducedB: Mar 22 | U5 B7 | Stakeholder Analysis + Stakeholder Voice AI Introduced

What you're submitting today

Three things: one stakeholder map row + counter-argument paragraph + 2-sentence response.

Stakeholder map row + counter-argument + response

(1) One fully-filled stakeholder-map row for your chosen stakeholder, all 6 fields: Who They Are · What They Want · Evidence They Cite · Position · Power · Allies+Opponents. (2) One counter-argument paragraph stating the strongest opposing view fairly, using the opposing stakeholder's framing and evidence (not yours). (3) A 2-sentence response to that counter without strawmanning: acknowledge what's legitimate, then articulate where you disagree on substance (not on the opposing stakeholder's competence or motives).

Submit via Google Classroom →

Rubric link: Today's counter-argument work is the T/T move the Position Paper's "Acknowledge competing concerns" section needs. T/T 7-8 requires "competing concerns acknowledged honestly." Strawmanning sits T/T in the middle bands. See the rubric.

One question before you leave

Three to five minutes. Your answer is saved to your reflection journal, where you can read back everything you have written this year.

Pick the honest answer over the polished one.

Today's reflection is in Google Classroom, under Reflection Journal.

Link posted in August

Sign in with your school account. Your teacher can see what you write here.