Part 9 of CrisisCore Build Log — Start here: https://dev.to/crisiscoresystems/testing-privacy-preserving-analytics-verifying-that-insights-dont-leak-identity-e37
This post links to Whitepaper v1.3.0 and gives a plain language summary so readers can decide quickly whether to read the full document. The summary focuses on architecture and scope and avoids claims that are not directly evidenced in the paper.
Summary Whitepaper v1.3.0 link plus plain language summary and a direct reading path for technical and non technical readers.
Next up: https://dev.to/crisiscoresystems/the-overton-framework-is-now-doi-backed-ko7
If you want privacy-first, offline health tech to exist without surveillance funding it: sponsor the build → https://paintracker.ca/sponsor
Pain Tracker whitepaper v1.3.0 (PDF)
I’ve published a publication‑grade whitepaper for Pain Tracker v1.3.0.
- Download: https://paintracker.ca/whitepaper
- GitHub Release: https://github.com/CrisisCore-Systems/pain-tracker/releases/tag/whitepaper-v1.3.0
This is a plain-language, privacy-first overview of the app’s goals and architecture (offline-first, local-first by default), plus the trust boundaries we do and don’t claim.
If you’re evaluating pain diaries for clinical use, or you’re building health tooling and want to avoid surveillance-by-default patterns, this may be useful.