Best effort, intentionally.
This is a one-person project maintained around a full-time job. There is deliberately no uptime SLA, support SLA, publication calendar or promise that every feature request will be implemented.
The advantage: there is also no committee, quarterly growth target or advertising obligation pushing the project to become noisier than it needs to be.
Maintenance priorities
- Security problems and seriously misleading facts.
- Time-sensitive official changes that affect voting, test preparation or user decisions.
- Broken core functionality.
- Accessibility problems that block use.
- Useful content improvements.
- Nice-to-have features.
What happens if life gets busy?
The sites may remain static for a while. That is one reason they are built to be useful without a backend. Wherever information is sensitive to change, users should be able to reach the official source directly.
A time-sensitive tool may eventually be marked Archived rather than pretending to be current forever. For example, an election guide can remain as a historical resource after the election while new election-specific claims stop being presented as live.
Current status
For actual product changes, use Updates. This page describes the maintenance model, not real-time server monitoring.