ZeitBoard

ZeitBoard is an early local-first scheduling prototype for people whose sleep-wake timing is free-running or highly irregular. It estimates an observed sleep-wake rhythm from user-controlled data, forecasts uncertain sleep and waking windows, and uses those forecasts to propose useful times for flexible tasks.

This repository is a phase-one scaffold. It is not a medical device, does not estimate DLMO or exact circadian phase, and does not recommend medication, light, melatonin, stimulant, hypnotic, meal, or exercise timing.

ZeitBoard is a separate project from the neighboring Zeitlog and Zeitdex workspaces. The shared zeit prefix is intentional branding, not shared code, history, or product scope.

Repository layout

apps/desktop                Wails v2 desktop application and React UI
apps/android                Native Android Compose companion
apps/trusted-web-prototype  Static synthetic trusted-view prototype
core                        Go domain, ingest, storage, estimation, and scheduling
contracts                   Versioned JSON Schemas
docs                        Product specifications, architecture, privacy, roadmap, and ADRs
scripts                     Reproducible setup, development, and fixture generation
testdata                    Synthetic observations and projected sharing fixtures

Phase-one status

The phase-one scaffold is implemented with synthetic fixture flows:

• Go core with provenance-preserving corrections, robust sleep-start drift estimation, uncertainty forecasts, scheduling proposals, medication-relative timing, SQLite storage, and default-deny sharing.
• Wails v2 Windows application with eight accessible React screens, an in-process collector boundary, and a Windows tray reopen/quit adapter.
• Native Android Compose application with visible fixture mode and Health Connect READ_SLEEP availability/permission flow.
• Static trusted-view prototype containing only pre-projected synthetic fields and no network requests.

Build and test

From the repository root on Windows:

.\scripts\setup.ps1
.\scripts\dev.ps1 -Action check -Component all

Direct component commands:

go test ./core/... ./apps/desktop/...
.\scripts\dev.ps1 -Action build -Component desktop
.\scripts\dev.ps1 -Action build -Component android

The setup and development scripts prefer the pinned local Node.js runtime under .tools. If running npm directly in a fresh shell, first put .tools\node-v24.16.0-win-x64 on PATH, or use the scripts above.

See docs/development.md for Linux commands, docs/verification.md for the verified environment, and docs/roadmap.md for real-source integration work. Android emulator launch requires an installed AVD; the debug APK can be built without one.