Every checklist here is a structured data file. Read it on a phone, print it at whatever size your kneeboard takes, or load it into your own software. Each one records the document it came from and whether a human has checked it against that document.
Using this from software
No API key, no rate limit, no registration. Plain HTTP paths:
api/index.json | The whole catalogue with metadata, verification state and rights per file |
api/checklists/<id>.json | One checklist, canonical form |
c/<id>/<id>.csv | Same content, one row per item, with a type column |
manifest.sha256 | SHA-256 of every published artifact, for verifying a mirror |
reviewed.txt | Files that a human has checked against their source |
unreviewed.txt | Files nobody has checked. Kept separate deliberately |
Validate any file against
schema/open-checklist-1.0.schema.json. Schema validity is necessary but
not sufficient — see what the states mean.