Evidence at a glance #
Based on the linked sources. The author's reported result and independent confirmation are separate checks.
- AI involvement
- Reported models: Claude. Tools: Python, JavaScript, Node.js. The writeup below describes the work attributed to AI.
- Reported result
- Works. This is the directory's source-based outcome classification.
- Independent confirmation
- Not reported.
- Human work and limitations
- The project explicitly notes that the captured snapshot of railwaycalendar.com is not committed due to copyright restrictions, requiring users to generate their own fixtures to reproduce those specific tests.
Original sources
What was done #
A reverse-engineered algorithm generating GB railway periods, possession weeks, and timetable years. The implementation includes a Python engine, a JavaScript port, and a static website, verified against three independent industry sources.
The GB Railway Calendar project provides a dependency-free algorithm to generate dates for railway periods, possession weeks, and timetable years. The author reports that the algorithm was entirely reverse-engineered from published outputs, specifically relying on data from railwaycalendar.com to form initial hypotheses. The implementation was systematically cross-checked against the Office of Rail and Road (ORR) railway period dates and the Planancy rail weeks calendar. The README documents that the full test suite results show 4,700 matches against railwaycalendar.com, 442 matches against ORR data, and 185 matches against Planancy. The project includes a Python engine and a line-for-line JavaScript port. Commits credit Claude Opus 5.5 as a co-author for the implementation, documentation, and licensing work. Limitations are noted in the repository, and while the algorithm covers financial years from 1995/96 to 2059/60, the project notes that timetable years and blocks rely solely on railwaycalendar.com for verification.
Reproduce it #
python run_tests.py