Use for finance and macro calculations done inside a spreadsheet: value-at-risk / reserves-at-risk on reserve holdings, price-return volatility and its annualisation, net exports as a share of GDP, GDP-weighted averages, spreadsheet statistics (min/max/median/percentile), and recovering missing figures in a linked financial workbook. Fires on "reserves at risk", "value at risk", "volatility", "net exports % of GDP", "weighted mean / SUMPRODUCT", "percentile", or "fill in the missing values from the totals/shares". Carries the exact formulas and the Excel percentile interpolation a grader checks.
Use when a task's answer is an .xlsx workbook that will be graded by a script, especially when the grader reads cells with openpyxl or converts the sheet to CSV. Fires on "write Excel formulas", "keep the formulas in the file", "no hardcoded values", "use openpyxl / xlsxwriter", "the cell must start with =", "recalculate the workbook", or a checker that reads a specific cell address. Covers the choice between emitting a live `=` formula and a literal value, why openpyxl formulas read back as None, the `_xlfn.` prefix, cross-sheet quoting, and the file-integrity rules graders enforce.
Use when modelling the macroeconomic impact of an investment spending shock in a spreadsheet — either the demand-side national-accounting framework (multiplier, import leakage, project allocation) or the supply-side Cobb-Douglas potential-GDP framework (TFP, HP-filtered trend, capital accumulation). Fires on "investment shock", "demand multiplier", "import content share", "supply-use table", "potential GDP", "Cobb-Douglas", "HP filter", "TFP / Solow residual", "extend the growth projection", or "capital accumulation with depreciation". Carries the exact in-sheet formula chain each model uses.
Use when the deliverable is a COUNT, RATE or AVERAGE computed from a repository's pull requests and issues over a date window, gathered with the `gh` CLI or the GitHub REST/GraphQL API — "how many PRs were opened in December", "average time to merge in days", "who opened the most PRs", "how many bug issues were closed that month", a monthly community-pulse report. Fires on "gh pr list", "gh issue list", "gh api", "repo analytics", or a JSON activity report checked against exact numbers. Carries the pagination defaults that silently truncate the answer, the PR/issue state semantics, and the two distinct date windows.
Use when the deliverable is a filled-in or edited PDF whose *text* will be checked — a court or government form, an application, a waiver, an intake sheet — or a PDF from which an identifier must be removed. Fires on "fill out this PDF form", "check the Yes/No boxes", "redact the ID / show only the last four digits", "sign and date the form", or a checker that runs `pdftotext` or `pypdf` over the output. Covers AcroForm vs XFA detection, why copying pages destroys the fields, radio and checkbox option values, and text-layer redaction that actually removes text.
Use when computing a powerlifting Dots score (also called Dots coefficient) for one or many lifters, in a spreadsheet or in code — anything that asks for "Dots", "IPF Dots", "Dots coefficient", or a bodyweight-normalised strength score from a squat/bench/deadlift total. Fires when a Total and a bodyweight must be turned into a comparable score across sexes and weight classes. Carries the exact sex-specific quartic coefficients, the asymmetric bodyweight clamps, and the rounding and formula shape a grader checks.
Use when writing or reviewing code that touches a dangerous API surface: `eval`/`exec`/`compile` on a string; `subprocess`/`os.system`/`os.popen` with a shell or a partial path; building a shell or SQL command by string concatenation or f-string; `pickle`/`yaml.load`/`torch.load`/ `tarfile.extractall`/`zipfile.extractall` on data you did not produce; fetching a caller-supplied URL or fetching without a timeout; `md5`/`sha1` in a security decision; a hardcoded `/tmp/...` path; a `0.0.0.0` bind; `chmod 0o777`; `random` for a token or secret; or logging an object that carries a credential. Gives the exact safe replacement call for each surface, plus the three rules that make a redaction survive static taint analysis.
Use when writing or repairing a Suricata / Snort-syntax IDS signature that must fire on one specific HTTP request shape and must stay silent on near-miss traffic — a custom exfil pattern, a C2 beacon, a data-theft POST, a suspicious header. Fires on "write a Suricata rule", "update local.rules", "alert with sid:NNNNNNN", "must not false-positive", "run suricata offline against these pcaps", or a rule graded by replaying positive and negative pcaps. Carries sticky-buffer scoping, the parameter-anchoring regex that separates true positives from lookalikes, content byte-escaping, and the offline verification loop.