Collective Agentic Practice
Anchoring What One Cannot Anchor Alone — Collective Agentic Practice
Type F (ambient) extensions are the hardest to anchor because they are not invoked by the user — they are present in the infrastructure, shaping cognition persistently and invisibly. This task asks you to pick ONE such feature in your own school's platforms and audit it. The critical move is from "AI is everywhere" (generic) to "this specific feature, in this specific platform, is doing this specific thing to this specific student population." Invisibility is the defining risk: agency cannot anchor what it does not see.
Key concepts:
- Type F extensions are infrastructural — not invoked by the user, but acting on them
- The audit must name a mechanism, not just an outcome — "the recommender weights engagement metrics" is a mechanism
- Subject-specific affected populations — not "all students" but e.g. "the EAL group who engage less with video recommendations"
Collective evaluation builds professional knowledge that no individual teacher could build alone. This task is deliberately cooperative: you must produce a shared artefact with at least one colleague. The rubric-significant element is the recorded disagreement — it is evidence that you engaged with a peer's judgment, not just assembled adjacent individual opinions. Consensus without friction is usually consensus without thought.
Key concepts:
- Collective agency is not aggregated individual agency — the shared artefact has to be authentically joint
- A recorded disagreement demonstrates actual engagement, not parallel monologue
- The "one insight neither of you had alone" is the epistemic payoff — it's why collective evaluation is a competency, not a convenience
Some risks cannot be fixed from inside the classroom — they require institutional decisions about procurement, policy, or governance. This task asks you to draft (you don't have to send it) a formal escalation to someone with institutional authority. The artefact is evaluated on whether it is actionable: a leadership colleague receiving this memo should be able to act on it without asking you further clarifying questions. Vague concerns get filed. Concrete asks get answered.
Key concepts:
- An escalation is not a complaint — it carries a concrete ask on a timeline
- Affected parties named specifically; evidence base cited
- The memo must make the risk institutionally legible — it translates classroom-level concern into decision-ready language
The teacher is a political agent in the conditions under which AI enters education — not merely an end-user of conditions others set. This task asks for substantive engagement with a real policy item: you take a position, defend it, and submit it (or prepare it for submission). A position paper that just restates the consultation's framing without taking a stand is not a response; it is compliance theatre.
Key concepts:
- Policy engagement is collective agency expressed through institutional channels
- A response has a stance — you agree / disagree / propose an alternative, and you say why
- Subject-specific grounding — your response draws on your actual teaching experience, not generic advocacy