Design a Hands-On Mathematics CPD Workshop

ROLE: Act as a mathematics CPD designer prioritising active rehearsal and classroom transfer.

CONTEXT: Design a [WORKSHOP LENGTH] session on [CPD GOAL] for [PARTICIPANT PROFILE] using [CURATED TOOL URLS].

INPUTS — FILL EVERY PLACEHOLDER:
- [WORKSHOP LENGTH]
- [CPD GOAL]
- [PARTICIPANT PROFILE]
- [CURATED TOOL URLS]
- [VENUE CONSTRAINTS]

SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [PHET] Exact verified whitelist entry: https://phet.colorado.edu/sims/html/graphing-quadratics/latest/graphing-quadratics_all.html?locale=en&screens=1. It selects the simulation and screen but cannot preload coefficient values. Do not invent other simulation slugs.
- [WOLFRAM_DEMONSTRATIONS] Exact verified whitelist entry: https://demonstrations.wolfram.com/QuadraticEquation/. Use no other Demonstrations slug unless it appears verbatim in a teacher-supplied or curated clicked table.
- [GEOGEBRA] Whitelist: https://www.geogebra.org/graphing|geometry|3d|cas?command={COMMANDS}. Define objects before annotations, separate commands with semicolons, encode only literal plus as %2B, print the commands as a fallback, and never invent /m/ material IDs.

DO THIS:
1. Create a short participant diagnostic tied to the CPD goal.
2. Plan a brief evidence-and-concept input followed by a longer hands-on build.
3. Use PhET and Wolfram Demonstrations only from [CURATED TOOL URLS].
4. Use GeoGebra command links for new constructions, never fabricated material IDs.
5. Add peer critique criteria and a classroom-adaptation task.
6. Define a later follow-up artifact or observation without collecting sensitive data.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Create a CPD tool task for exploring how a changes y=a*x^2.
Expected result or check target: Participants predict, build, inspect, critique, and adapt a parameter graph for their classes.
check this yourself
CHECK → https://www.geogebra.org/graphing?command=a=1;f(x)=a*x^2;Extremum(f)
(paste-fallback: a=1;f(x)=a*x^2;Extremum(f))
Encoding note: The payload contains no literal plus sign; parentheses, equals, caret, asterisk, and semicolons remain literal under the GeoGebra exception.

OUTPUT FORMAT:
1. Participant Diagnostic — needs and starting points
2. Workshop Agenda — timed active sequence
3. Tool Task — tested build and fallback
4. Peer Critique — criteria and protocol
5. Classroom Adaptation — participant transfer artifact
6. Follow-Up Evidence — privacy-safe implementation check

QUALITY AND TOOL GUARDRAILS:
- Use only exact supplied curated PhET and Demonstration URLs; never invent slugs or permalinks.
- Never invent GeoGebra /m/ IDs; use ?command= links with exact fallbacks.
- Check current policy, syllabus, and professional-credit claims at dated official sources.
- Test every tool on venue devices and supply a no-network fallback.
- Do not promise participation certificates, accreditation, or impact without authority and evidence.
- 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.