Why the product exists
People with atypical schedules often live through weeks that look ordinary on paper while quietly eroding sleep, recovery, and social time. Shiftwell tries to make that erosion visible, readable, and discussable.
Making visible what irregular weeks quietly wear away.
Shiftwell tries to make visible what night weeks, split schedules, and unstable rhythms slowly wear down. The project stays modest in its claims, but wants to be strong in legibility.
People with atypical schedules often live through weeks that look ordinary on paper while quietly eroding sleep, recovery, and social time. Shiftwell tries to make that erosion visible, readable, and discussable.
The current engine is a proxy MVP. It is documented, traceable, and imperfect by design. It prefers to state what it approximates rather than pretend to have clinical precision it does not yet have.
Shiftwell relies on third-party scientific references and local working copies to compare, map, and explain its engine. Those materials remain external to the project: no authorship or ownership is claimed.
Shiftwell is moving by trying to hold together three tensions that often pull apart: a simple interface, a formula honest enough to be trusted, and documentation clear enough that others can audit or contribute without guessing the project logic.
Shiftwell is not a diagnostic tool. It structures work/sleep collection and produces indicative scores in a research setting, with a strong emphasis on explainability.
Local computation reduces friction, supports open-source use, and limits backend dependency. Study contribution comes later with explicit consent.
The direction stays the same: a stronger engine, a richer factor trace, then an interface that helps people understand a week instead of just showing numbers.
Next.js static export, Cloudflare Pages, GitHub Actions, and Wrangler. The stack stays intentionally light so the project remains easy to distribute and contribute to.