# Plan: Consolidated "Technologies That Help" grid (Michael's taxonomy)

**Spec/review:** Opus · **Coder:** Sonnet · **Skills:** ponytail, karpathy, honey
**Source:** Michael Miller's assignment-category grid (Written / Multiple Choice / Problem-based x 9 types). Tools from `standards/asu-assessment-tools.md` (Wes-approved) + Honorlock/Respondus (last resort).

## Goal
Replace the five scattered per-category "Technologies That Help" lists in `scripts/assessment_design_playbook.py` with ONE consolidated grid laid out like Michael's image: three family columns, nine assessment-type cells, each cell listing that type's approved tools with key caveats.

## Scope (ponytail: one structural change + author 9 cells)
1. In `scripts/assessment_design_playbook.py`:
   - Remove the per-category `"tech"` rendering (the `Technologies That Help` `<ul>` inside each `.category-block`, render loop ~285-286). Keep every other subsection (Where It Is Substitutable, AI-Forward Moves, AI-Resistant Moves, The Anchor) untouched.
   - Keep the `"tech"` data keys on the category dicts OR remove them — coder's call; simplest is to stop rendering them and delete the now-unused key + its render line. Do not delete the other keys.
   - Add ONE consolidated section titled **Technologies That Help** after the category blocks, rendering the 9-cell grid in §Grid content below.
   - Add CSS: a `.tech-grid` (CSS grid, 3 equal columns, gap) of `.tech-cell` cards, each with the type name (bold) + a compact tool list. Match the existing warm-neutral/maroon design tokens already in `_CSS`. Print: the grid should not break awkwardly (`break-inside: avoid` on cells).
2. No change to `standards/asu-assessment-tools.md` (already has all tools incl. Honorlock/Respondus).

## Non-goals / deferred
- Do NOT re-taxonomize the playbook BODY into 9 categories. The body keeps its current 5 categories (Discussions, Quizzes & Exams, Papers, Projects, Presentations) with their design-guidance subsections. Only the tech section consolidates into the grid. (Full body re-taxonomy is a separate, deferred decision.)
- Keep Michael's family label "Multiple Choice" verbatim (he asked to use his categories); do not relabel.
- Presentations is not in Michael's grid and gets no cell; leave its body one-pager as-is.
- No version/CHANGELOG bump (release after review). No em/en dashes (use `--`).

## Grid content (author these 9 cells verbatim)
Three columns: **Written**, **Multiple Choice**, **Problem-based**. Each cell = the type name then its tools, each tool with a short use/caveat.

**Written**
- **Discussions** -- EdDiscussions (gated posting, cohort-specific prompts); VoiceThread (voice/video, identity signal); Harmonize (peer-review discussions; AI-coaching caveat); Yellowdig (participation only, not authorship).
- **Reflections / Learning Journals** -- VoiceThread (recorded reflection, identity signal); Canvas Assignments (journal entries with rubric); H5P (formative reflection prompts; not a graded anchor).
- **Papers** -- Harmonize (staged draft, peer review, revise = authorship trail); VoiceThread (recorded defense of the paper); Canvas Assignments (rubric + a required draft milestone).

**Multiple Choice**
- **Quizzes** -- Canvas New Quizzes (item banks, randomization, time limits); iClicker or Top Hat (formative checks, sync-only).
- **Exams** -- Canvas New Quizzes (large randomized application pool); Honorlock or Respondus LockDown Browser (last resort, high-stakes only; equity + surveillance cost, not AI-proof).
- **Problem Sets, Labs, Procedural Tasks** -- Canvas Assignments or New Quizzes (parameterized items); WeVideo/PlayPosit (embedded procedural checks); H5P (branching or drag-and-drop practice; formative).

**Problem-based**
- **Case Analysis** -- Harmonize (multi-stage submission + peer review); VoiceThread (recorded analysis or defense); Canvas Assignments (rubric + staged milestones).
- **Projects** -- Harmonize (milestone check-ins + peer review); VoiceThread (each member narrates their contribution); Canvas Assignments (dated process log or, for code, commit history alongside).
- **Portfolios** -- Harmonize (multimedia portfolio + peer review); VoiceThread (narrated portfolio walkthrough); Canvas Assignments (artifacts staged over time).

A one-line note under the grid: proctoring tools (Honorlock, Respondus) are the only identity controls and are a last resort; formative-only tools (H5P) support practice but cannot be the graded anchor.

## Acceptance criteria
1. The playbook renders ONE consolidated "Technologies That Help" grid with exactly 3 family columns and 9 type cells, content per §Grid.
2. No per-category "Technologies That Help" `<ul>` remains inside the category blocks.
3. Only Wes-approved tools + Honorlock/Respondus appear; none of Examity, Perusall, Hypothesis, Turnitin, Canvas Studio, Flip, Mobius, WeBWorK, GitHub, Zoom, Padlet anywhere in the file.
4. No em/en dashes (use `--`); dash-lint test green.
5. Full suite green: `.venv/bin/python3 -m pytest tests/ -q`. Update `tests/test_assessment_design_playbook.py` where it asserts on the old per-category tech structure; do not weaken unrelated tone/TILT/forward-resistant assertions.

## Verify (reviewer, Opus)
Regenerate the playbook; confirm the single 9-cell grid renders in the 3-family layout, the per-category tech lists are gone, tools/caveats match §Grid, and no dropped tools appear. Read the diff; re-run the full suite. Coder != reviewer.

## Workflow
Feature branch → implement → full suite green → PR against `main` (`gh pr create`), do NOT merge. ponytail/karpathy/honey: only the tech-render swap + the grid + its CSS; terse. Report branch, PR#, verbatim pytest line, files changed, a grep confirming the grid cells + absent dropped tools, any criterion unmet.
