AI Anonymous · from JAB Systems October 22, 2026 — Crossref citation triage practice Prerequisite: Python 3.13 available as python; internet access to api.crossref.org. No third-party Python packages, AI account, or API key required for this exercise. Read check-citations.py and citation-fixtures.json before running. From this extracted folder in Windows PowerShell: python .\check-citations.py | Set-Content -Encoding utf8 .\my-citation-results.json Get-Content .\my-citation-results.json The code sends two public DOI strings to Crossref, with a one-second gap. The repeated real DOI is cached in memory for this run. No AI answer or claim text is sent. It prints JSON; the command saves a local report. On HTTP429/other service errors or timeout it reports unresolved and stops. Back off and investigate before retrying; no automatic retry loop is included. For ongoing use, follow Crossref etiquette, including your own valid contact information and persistent caching. This is a tiny demonstration, not a bulk tool. Observed on Windows/Python3.13.15 October22: matching_metadata_title → record_returned/title_agrees; deliberately_wrong_title → record_returned/ title_differs; authored_missing_identifier → not_in_crossref/HTTP404. All three claim_support values remain not_checked. Exit0 means report produced, not citation approved. Network/API results and metadata may change. Fixtures are authored. The wrong title and missing identifier are deliberate. 404 is scoped to Crossref, not a claim that a DOI cannot exist elsewhere. Whitespace/case normalization only; publisher subtitles/formatting may differ. Review authors/year/source passage and updates separately. No model tested.