Krest reads a private board or an available local calendar. The public website uses a fictional fixture only.
Day can read Calendar Control’s existing local Google export at ~/.config/calendar-control/google-snapshot.json. It shows the capture time, coverage and stale state. Checking the file every minute does not renew Google authorization or fetch a new export.
When that file is absent, Krest can use macOS Calendar with calendar permission. It reads events and never edits them. Calendar Control remains a separate application.
To connect a board you control:
defaults write org.aimindset.krest.bar KrestURL "https://your-private-board.example"Reopen Krest after changing the address. It reads контекст.json from that address. Board balance and local calendar estimates remain separately labelled; calendar differences are visible in Day.
To return to the local calendar, remove the board setting and reopen:
defaults delete org.aimindset.krest.bar KrestURLThe open-source board engine assembles source records into four arms. Each record has a stable ID, text, source, time offset, weight, scope and optional reframing prompt.
Schema keys remain in the original format for compatibility: дата (day), собрано (capture time), лучи (arms), баланс (x/y), источники (source receipts) and правила_версия (rules version). Missing or invalid readings are not evidence of zero activity.
Weights reflect declared rules. A change in a snapshot shows that the recorded model changed; it does not prove which event caused that change.
The app saves aggregate observations in ~/Library/Application Support/Krest/history-v1.json. Different boards and the local calendar have separate histories. The app writes atomically, deduplicates capture timestamps and preserves an unreadable original file.
A board can expose an HTML directory listing at /история/ containing YYYY-MM-DD.json snapshots. Krest reads up to 366 daily archive files. It does not manufacture missing dates.
For a past event, Reflect opens the board’s existing response form. Event and date are prefilled; the user chooses how it affected them. A scheduled end time is not evidence that a commitment was completed.
Within Krest, a one-minute check refreshes available sources and recalculates event phases. Opening the panel and waking the Mac also trigger a check. Freshness always follows the original source receipt.
The balance dot uses observed coordinates. A successful check has one 650 ms visual response. Shared voxel gestures are finite and respect system Reduce Motion. The web field settles after an interaction and pauses when hidden.