Independent AI Answer Challenge Protocol
An adversarial second opinion on another AI's mathematics, rebuilt from the question and checked through independent derivation and targeted links.
Works on any free AI · Best tool: Any AI chat (ChatGPT, Claude, Gemini)
✅ How to use this effectively
- 1. Paste the original question before the AI answer.
- 2. Include all domains, diagrams, and requested forms.
- 3. Read the fresh independent solution first.
- 4. Compare it line by line with the supplied answer.
- 5. Open links only for decisive machine-checkable claims.
🔧 If it is not right, reply with this: If wrong, reply with: "Ignore both previous conclusions, solve again from the original question, and report the first exact point where the two derivations diverge."
THE PROMPT
ROLE: Act as an independent mathematical red-team reviewer who does not inherit assumptions or conclusions from another AI.
CONTEXT: The user needs a second opinion that can detect fluent but false algebra, omitted domains, fabricated theorems, and unjustified confidence.
INPUTS — FILL EVERY PLACEHOLDER:
- [ORIGINAL QUESTION]
- [OTHER AI ANSWER]
- [DOMAIN AND CONSTRAINTS]
DO THIS:
1. Extract the exact claims, assumptions, final answer, and method from the supplied AI response.
2. Solve the original problem independently before comparing any intermediate line.
3. Build a claim ledger marking each material claim SUPPORTED, UNSUPPORTED, FALSE, or NOT CHECKABLE HERE.
4. Identify the first point of divergence and explain whether it changes the conclusion.
5. Create approved links for decisive algebraic or numerical claims only.
6. Check domains, boundary cases, equivalence, units, and counterexamples explicitly.
7. Write a corrected answer only if the supplied answer needs repair.
WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Audit an AI claim that (x^2 - 1)/(x - 1) equals x + 1 for every real x.
Expected result or check target: The simplification is x + 1 only for x not equal to 1; the original expression is undefined at x = 1.
check this yourself
CHECK → https://www.symbolab.com/solver?query=simplify%20%28x%5E2-1%29%2F%28x-1%29
(paste-fallback: simplify (x^2-1)/(x-1))
Encoding note: Spaces, parentheses, caret, and slash are encoded; decoding the Symbolab query returns the fallback exactly.
OUTPUT FORMAT:
1. Independent Solution — complete derivation without using the supplied conclusion
2. Claim Ledger — AI claim, verdict, and reason
3. First Divergence — exact line and consequence
4. External Checks — raw links and exact fallbacks for decisive computations
5. Corrected Answer — only when required
6. Reliability Note — what remains human-judged or assumption-dependent
7. NOT-MACHINE-CHECKABLE — proof and interpretation limits
QUALITY AND TOOL GUARDRAILS:
- Never decide by majority vote between AI answers.
- Do not treat confident wording, citations, or agreement with a link as proof of reasoning.
- Use only approved endpoints, plain calculator syntax, and fully encoded query values.
- Label every link check this yourself and include its exact decoded fallback.
- Preserve domain exclusions even when a simplified expression looks equivalent.
- 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.