01 / CONTEXT
The problem to solve
Make frequently updated public COVID-19 statistics accessible through a simple API.
02 / ENGINEERING
From need to system
- Use the Johns Hopkins CSSE public dataset as a source.
- Refresh the dataset on a scheduled interval.
- Expose historical and current data through Flask endpoints.
- Archive the project as a snapshot of an early data-service implementation.
03 / DESIGN DECISION
A meaningful choice
Separate data collection from API access so consumers can query a consistent service interface.
04 / EVIDENCE AND LIMITATIONS
What is actually documented
The public README documents the Flask API, JHU CSSE source and a scheduled refresh roughly every ten minutes. The repository is archived and is not presented as a current public-health source.
05 / NEXT VALIDATIONS
How I would strengthen the proof
- Point users to current authoritative public-health sources.
- Add source timestamps and data freshness indicators if revived.
- Review historical API behavior before reuse.
These are planned validation steps, not already measured results.