Which 1:30 did AI mean? — October 25, 2026
Read check-wall-time.py and wall-time-cases.json before execution.
Requires an existing Python installation with venv/pip. Tested Windows Python 3.13.15 and tzdata 2026.5.
Create an empty folder, download/extract this kit, then create a local virtual environment:
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install tzdata==2026.5
.\.venv\Scripts\python.exe .\practice\check-wall-time.py

Installation requires network access. No API key/model/calendar/provider required. The checker reads adjacent fictional JSON and prints a report. It forces the installed tzdata package by disabling the system TZPATH. No real meetings or calendar writes.
Seven authored cases: ambiguous, nonexistent, unique, unique UTC control, unknown zone, invalid input, supplied offset outside demo input contract.
The offset-bearing case is deliberately not analyzed; it is not a claim that offset-bearing timestamps are invalid. The checker expects offset-free ISO local dates/times plus a named zone; it is not a strict RFC3339 or natural-language parser. Unexpected fixture structure can stop the script.
Exit 0 means the report was produced, not that all cases are usable times.
Report records Python/data package version. Future data changes can alter civil-time results. The proposed AI extraction prompt has not been run/evaluated.
Virtual environments isolate dependencies, not code permissions. Review downloaded code; no sandbox/safety guarantee.
Guide: https://jabsystems.io/ai-anonymous/ai-check-the-wall-time
Social files are for manual posting only. Nothing scheduled/published to social.
