# Plan: ASU assessment-tools reference + recommendation wiring

**Spec/review:** Opus · **Coder:** Sonnet · **Skills:** ponytail, karpathy, honey
**Source:** `Assessment Tools Quick Reference.pdf` (ASUO IDs / TILT team). Content is captured in §Data below so the coder needs no PDF access.

## Goal
Give the recommendation-making skills a canonical map of **ASU-supported** assessment tools → assurance levers, so a "secure an anchor" or design recommendation names a real ASU tool instead of a generic move.

## Scope (ponytail: smallest change that delivers this)
1. **New** `standards/asu-assessment-tools.md` — a concise reference (markdown only, no scripts, no data model). Content = §Data below.
2. **Wire two one-line references** to it (minimal-diff, do not rewrite the host sections):
   - `standards/assessment-assurance-design.md` — the choke point every generator inherits "secure an anchor" from (per CLAUDE.md §Assurance by Design). Add one line in the design-levers area: when naming a securing/design move, prefer a tool from `standards/asu-assessment-tools.md` and honor its caveats.
   - `skills/assurance-audit/SKILL.md` — Step 5 (recommendation authoring). One line: name the ASU tool from the reference for each recommended move where one fits.
3. Nothing else. Do NOT touch generators individually (they inherit via the standard), do NOT add a script or a test framework.

## Non-goals
- No per-tool automation, no LTI config code, no scraping. Pure reference + two links.
- No version bump/CHANGELOG (release handled after review).

## `standards/asu-assessment-tools.md` — required structure
A short intro line (what it is, that TILT owns implementation), then a table with these columns, one row per tool:

`Tool | Secures a graded anchor? | Design use | Graded + gradebook passback | Sync/async | Caveat`

Then a short "How to use in recommendations" list capturing the four critical reads.

Classification (this is the ID value-add — get it right):
- **Harmonize** — Secures: **Yes (strong)**, multi-stage draft→peer-review→revise = documented authorship/process trail + video/screenshare. Design: authentic + AI-forward-capable (built-in AI coaching). Graded+passback: Yes, LTI. Async. Caveat: **built-in AI coaching conflicts with a no-AI course policy** — disable it or use it to move that course to AI-forward.
- **VoiceThread** — Secures: **Yes**, recorded voice/video response = authorship/identity signal (async oral, narrated slides). Design: authentic. Graded+passback: Yes, LTI. Async. Caveat: not AI-proof (deepfake), but a strong async authorship signal.
- **Canvas (Classic/New Quizzes, Assignments)** — Secures: **Partial** — New Quizzes item banks + randomization/parameterization is the exam securing lever; native rubrics/SpeedGrader for written work. Design: any. Graded+passback: Native. Async. Caveat: no native proctoring; timing alone is not securing.
- **WeVideo (PlayPosit)** — Secures: No (engagement evidence only), gated embedded video Qs. Design: formative comprehension. Graded: optional, passback. Async. Caveat: formative.
- **EdDiscussions** — Secures: No, but supports gated posting + cohort-specific binding (discussion design lever). Design: authentic discussion. Graded: optional, passback, LTI. Async.
- **Yellowdig** — Secures: No, participation points (engagement, not authorship). Graded: yes, passback, LTI. Async.
- **iClicker** — Secures: identity signal only when **synchronous**. Graded: optional, passback, LTI. Sync (async limited to formative). Caveat: sync-only value for ASU Online.
- **Top Hat** — same profile as iClicker (polling + interactive content). Sync. Caveat: sync-only value.
- **H5P** — Secures: **No — formative only**, no gradebook/LTI (embed code). Design: branching scenarios, knowledge checks (application practice). Async. Caveat: **cannot be a graded anchor.**
- **Google Workspace (Forms)** — Secures: No — formative, no passback, no LTI. Caveat: cannot be a graded anchor.
- **Inscribe** — Secures: No — community/knowledge base, not graded, no LTI. Caveat: not an assessment anchor.
- **Orchard** — In development (EdPlus). Graded/passback/LTI: TBD. Caveat: not available yet.

Four critical reads (put in the "How to use" list):
1. No proctoring/surveillance tool is in ASU's supported set — this reinforces authorship-first, proctoring last resort.
2. **Gradebook passback is the filter** for "can be the secured anchor": H5P, Google Forms, Inscribe, Orchard fail it — never recommend them AS the anchor.
3. **Harmonize AI coaching vs a no-AI policy** is a real conflict — name it before recommending Harmonize into a prohibition course.
4. Synchronous tools (iClicker, Top Hat) are not securing controls for async ASU Online.

## Acceptance criteria
1. `standards/asu-assessment-tools.md` exists with the table (all 12 tools, all 6 columns) and the four critical reads.
2. `standards/assessment-assurance-design.md` and `skills/assurance-audit/SKILL.md` each contain a reference (relative path) to the new file; the referenced path resolves.
3. No em/en dashes in authored prose (repo house rule — use `--`); keep any dash-lint test green.
4. Full suite green: `.venv/bin/python3 -m pytest tests/ -q`. If a test validates standards-doc cross-references/existence, it passes; only add a new test if such a pattern already exists (ponytail: no new test framework for a docs change).

## Workflow
Feature branch → implement → run full suite → PR against `main` (`gh pr create`), do NOT merge. Apply ponytail/karpathy/honey: shortest doc that carries the map, minimal-diff wiring, terse. Report branch, PR#, verbatim pytest summary, files changed, and any criterion not met.
