Homework Submission Form With Self-Check Links

ROLE: Act as a homework workflow designer, link verifier and Google Forms submission developer.

CONTEXT: A teacher wants students in [CLASS] to submit work for [HOMEWORK SET], check computable answers themselves and explain one correction.

INPUTS — FILL EVERY PLACEHOLDER:
- [CLASS]
- [HOMEWORK SET]
- [SUBMISSION DEADLINE]
- [STUDENT IDENTIFIER POLICY]
- [EVIDENCE FORMAT]
- [MARKS OR COMPLETION POLICY]

DO THIS:
1. Transcribe the homework exactly and identify which answers are suitable for a solver self-check.
2. Create one correctly encoded check-this-yourself link and paste fallback for each computable item, while flagging proofs and explanations for human review.
3. Design an attempt-first sequence with response fields, self-check instructions and one required correction reflection.
4. Generate one complete executable FormApp script with student identifier according to policy, response fields, help text, confirmation message and logged URLs.
5. Do not require a file-upload item; if evidence is external, collect only a teacher-approved share link or typed work description.
6. Add a teacher review table separating completed, corrected and needs-feedback submissions.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Create a submission form for homework containing x^2-9=0.
Expected result or check target: The self-check returns x=-3 or x=3, and the student records any correction after making an independent attempt.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=solve%20x%5E2-9%3D0
(paste-fallback: solve x^2-9=0)
Encoding note: The space is %20, ^ is %5E and = is %3D.

OUTPUT FORMAT:
1. HOMEWORK-TO-CHECK MAP
2. SELF-CHECK LINK TABLE
3. ATTEMPT–CHECK–CORRECT PROTOCOL
4. COMPLETE GOOGLE APPS SCRIPT
5. RUN IT — script.google.com → New project → paste → Run → View → Logs
6. TEACHER REVIEW TABLE

QUALITY AND TOOL GUARDRAILS:
- Output one COMPLETE executable FormApp code block and print exactly: script.google.com → New project → paste → Run → View → Logs.
- Never claim a URL creates the form, and do not ask FormApp to create an unsupported file-upload workflow.
- Label every maths link check this yourself and state that proofs and written reasoning still need human review.
- Collect only the student identifier and evidence the teacher explicitly requests.
- 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.