Issue an Error-Analysis Link From Anonymous Work

ROLE: Act as an assessment-for-learning designer using anonymous mathematical work.

CONTEXT: The class will inspect [ANONYMOUS STEPS] from [TOPIC] and learn to classify and repair the error.

INPUTS — FILL EVERY PLACEHOLDER:
- [TOPIC]
- [ANONYMOUS STEPS]
- [EXPECTED METHOD]
- [TRANSFER SKILL]

SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [CLAUDE] Whitelist template: https://claude.ai/new?q={ENCODED_PROMPT}. It prefills for review and does not auto-submit; login is normally required, so provide the exact prompt as a paste fallback and never encode personal data.

DO THIS:
1. Copy the anonymous steps exactly into a compact student prompt.
2. Ask for the first invalid line, error category, and corrected step.
3. Distinguish observable evidence from guessed misconception.
4. Build a Claude source-bound prefill URL below 1,800 characters.
5. State that the link prefills only, must open in a browser, and requires review plus Send.
6. Add one approved symbolic check for the disputed expression.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Analyse the false simplification (x+2)^2=x^2+4.
Expected result or check target: The exercise identifies the missing 4x term, classifies incomplete expansion, and supplies a transfer item.
check this yourself
CHECK → https://www.symbolab.com/solver?query=%28x%2B2%29%5E2-x%5E2-4
(paste-fallback: (x+2)^2-x^2-4)
Encoding note: Parentheses, the plus sign, and carets decode from %28/%29, %2B, and %5E to match the fallback exactly.

OUTPUT FORMAT:
1. Anonymity Audit — excluded information
2. Error-Analysis Prompt — exact text
3. Student Link — raw Claude prefill URL
4. Teacher Key — observed error and correction
5. Independent Check — check this yourself

QUALITY AND TOOL GUARDRAILS:
- Never encode handwriting images, names, marks, comments, device IDs, or other identifying data.
- Do not infer ability, effort, diagnosis, or intent from an error.
- Claude prefill does not auto-submit and must stay under 1,800 characters.
- Preserve the supplied line order and notation exactly.
- External computation checks algebra only, not the learner hypothesis.
- Copy every [PLACEHOLDER IN SQUARE BRACKETS] character-for-character in every template, code block and translated variant.
- Never output a desmos.com URL with parameters, a mathsolver.microsoft.com URL, an invented GeoGebra material ID, an invented DIKSHA code, an invented Khan topic path, or an unlisted quiz or simulation slug.
- Never describe an AI answer as verified. Every external check must be labelled “check this yourself” for the teacher or student to inspect personally.
- Do not invent exam facts, source citations, marks distributions, tool IDs or inaccessible links. Separate mathematical proof from computational checking.

=== TOOL-LINK OUTPUT CONTRACT — follow every rule exactly ===
1. You may output clickable links ONLY to: wolframalpha.com/input?i= · symbolab.com/solver?query= ·
   geogebra.org/graphing|geometry|3d|cas?command= · math.stackexchange.com/search?q= · oeis.org/search?q= ·
   artofproblemsolving.com/community/q1_ · khanacademy.org/search?page_search_query= ·
   overleaf.com/docs?encoded_snip= · latex.codecogs.com/png.image? · docs.google.com/forms/...viewform?usp=pp_url
   (Forms only with entry.N IDs I paste in) · plus any URL I give you or that appears in this prompt's whitelist table.
2. NEVER output: desmos.com links with query strings (they load blank), invented geogebra.org/m/ IDs, Khan topic
   URLs, DIKSHA dial codes, Wolfram quiz/demo slugs not in my table, or mathsolver.microsoft.com (dead site).
3. Write queries in plain calculator syntax (x^2, sqrt(x), pi, 3/4) — never LaTeX — EXCEPT Overleaf and CodeCogs
   payloads, which are LaTeX.
4. Percent-encode the query part: space→%20, +→%2B, ^→%5E, =→%3D, [→%5B, ]→%5D; in LaTeX payloads also
   \→%5C, {→%7B, }→%7D, %→%25, #→%23, &→%26, newline→%0A. GeoGebra ?command= exception: encode ONLY + as %2B;
   leave ( ) = ^ ; as typed.
5. One link per line, formatted exactly:  CHECK → <full raw URL>   (no markdown brackets, nothing after the URL).
6. Directly below every link, print:  (paste-fallback: <the un-encoded query or commands>)
7. Before printing any link, silently decode your own URL and confirm it reproduces the query character-for-character;
   rebuild it if not. If a URL would exceed 1,800 characters (Overleaf: 6,000), print only the paste-fallback.
8. Label every link "check this yourself" — never claim the link proves your answer is correct.
9. On phones these links must be opened in a browser, not an installed app — say this once at the end.