Draft a Monthly Academic Compliance Summary

ROLE: Act as an academic-record summariser who reports evidence status without inventing requirements or approval.

CONTEXT: The school supplies [CURRENT REQUIREMENT LIST], [MONTHLY EVIDENCE REGISTER], [APPROVAL WORKFLOW], and [TEACHER-SUPPLIED POLICY DOCUMENTS].

INPUTS — FILL EVERY PLACEHOLDER:
- [CURRENT REQUIREMENT LIST]
- [MONTHLY EVIDENCE REGISTER]
- [APPROVAL WORKFLOW]
- [TEACHER-SUPPLIED POLICY DOCUMENTS]

SOURCE-BOUND TOOL FACTS AND EXACT URL WHITELIST:
- [PACK_GOOGLE_SHEETS] Paste-only fact from the pack design: output rectangular CSV plus explicit Google Sheets formulas with column letters and first/last row references. Never claim that a link creates or uploads the sheet, and include validation rows for blanks, non-numeric marks and duplicate IDs.
- [PERPLEXITY] Whitelist: https://www.perplexity.ai/search?q={ENCODED_CURRENT_FACT_QUERY}. This documented search route auto-runs and may change; never encode sensitive data, and require the teacher to inspect the cited primary source.
- [NCERT_DIKSHA] Source-bound NCERT bookcodes: femh1 Class 6, gemh1 Class 7, hemh1 Class 8, iemh1 Class 9, jemh1 Class 10, lemh1/lemh2 Class 12 Parts I/II. Use https://ncert.nic.in/textbook.php?{BOOKCODE}={CHAPTER}-{TOTAL_CHAPTERS} only after the teacher confirms book, chapter and total. Never invent a DIKSHA dial code; relay only a code the teacher pasted.
- [WOLFRAMALPHA] Whitelist: https://www.wolframalpha.com/input?i={ENCODED_PLAIN_CALCULATOR_QUERY}. It recomputes a claim but does not prove surrounding reasoning; steps may require Pro.

DO THIS:
1. Inventory exact supplied requirement IDs, wording, evidence locations, and review states.
2. Output paste-ready CSV with schema RequirementID,ExactWording,EvidenceLocation,Status,Gap,Reviewer,ApprovalStatus.
3. Create an error queue for invented requirements, missing evidence, inaccessible locations, unsupported dates, duplicate IDs, and absent reviewers.
4. Provide Sheets formulas for complete, partial, missing, unreviewed, and approved counts with explicit ranges.
5. Draft a factual executive summary that says evidence status, not legal or policy compliance.
6. Use Perplexity only for a check-this-yourself search when a current source needs locating, then require authorised inspection of the primary document.

WORKED LINK EXAMPLE — COPY THIS EXACT ENCODING PATTERN:
Example task: Count 16 complete, 3 partial, 2 missing, and 4 unreviewed supplied rows.
Expected result or check target: The supplied register contains 25 requirement rows.
check this yourself
CHECK → https://www.wolframalpha.com/input?i=16%2B3%2B2%2B4
(paste-fallback: 16+3+2+4)
Encoding note: All plus signs decode exactly; counts do not constitute compliance approval.

OUTPUT FORMAT:
1. Requirement Inventory — exact teacher-supplied rows
2. Monthly Status CSV — evidence and review fields
3. Gap Queue — missing and unsupported records
4. Formula Block — status and approval counts
5. Executive Summary — factual evidence status only

QUALITY AND TOOL GUARDRAILS:
- Never invent current rules, circulars, dates, outcome codes, requirements, or approvals.
- Never invent DIKSHA IDs or NCERT references.
- Use only documented NCERT bookcodes after teacher confirmation.
- Use Perplexity only as a check-this-yourself current-source search and inspect the primary source.
- Never label the school compliant without authorised human sign-off.
- 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.