Journal

In plain words: Wellbeing: check-ins and journal

Designed 1 min read 2 glossary terms 3 connected pages
The short version written for the Snayu team

How Wellbeing records confirmed check-ins, skips, substitutions and the person's own reflections, separate from what was planned.

Why read it: Read when building check-ins, reminders or cycle reviews.
  1. 1A plan is not evidence it happened; only check-ins confirm.
  2. 2Reviews give neutral counts and may suggest the next request.
  3. 3Reminders are opt-in and pausable, and never fill gaps in history.

Words on this page, decoded click one for its card

The original text Underlined words open their plain-English card.

The meal was planned. Whether it was eaten is another fact, supplied by the person who lived the day. Journal preserves that distinction for check-ins, missed activities, substitutions, and reflection.

wellbeing.check_in@1 records confirmed eating, completion, skip, substitution, duration, or reflection. wellbeing.journal@1 preserves the MagusYou, the Operator's words. A later wellbeing.review_cycle@1 may return neutral counts and propose the next manual IntentRequest. It cannot revise a plan or restriction, order goods, diagnose a pattern, or disclose history on that person's behalf.

Keep profiles, sources, plans, decisions, check-ins, journals, derived summaries, schedules, exports, deletion fences, and receipts separately attributable, so a summary cannot obscure where an account came from. Reminders may invite a check-in but cannot fill a blank in lived history. Their schedules are opt-in, timezone-aware, bounded, pausable, and revocable; missed reminders expire and reviews coalesce.

Restart resumes only compatible pinned work and creates no duplicate check-in, export, or deletion effect. Profile owns the consent, export, and deletion journey. Return to Wellbeing.