Overview
A Mission is a health action you have approved. Its identity is a durable definition, its content is a dated revision, and its result for one local date is an occurrence. That three-part structure is what lets you edit a recurring mission today without rewriting what last Tuesday meant.
The coach can propose missions. It mostly cannot create them. This page is about where that line sits.
How it’s calculated
The two automatic paths
Requiring a second approval before your very first action would leave a new user holding proposals instead of a protocol, so exactly two product moments count as narrow authorization:
- Activating your goal during onboarding creates a bounded starter set from eligible, code-owned mission templates. It can use your goal and onboarding answers, and it cannot invent an unbounded recurring target.
- Submitting a Condition Check-In may create at most one AI-authored mission for that current local date.
The boundary ends there. Every other AI-authored recurring addition, edit, or retirement stays a pending proposal until you approve it, and neither automatic path may silently rewrite a mission you already have.
What bounds a proposal
The limit on the coach is what may judge the mission, not what the catalog happens to lack:
- A custom draft verifies manually, and may link one of your existing diary tags. Both are readable without new wiring, so a proposal cannot claim a source Grio has not proven it can read.
- A record signal requires a published template: Nutrition, hydration, step, weight, and workout verification reaches a proposal only through a vetted candidate that a readiness policy has bound.
- An unsolicited proposal requires source-labelled evidence: “The model judged it necessary” is not a reason.
- At most six proposals may be pending at once, across every origin.
This is a limit on the coach, not on you. The metric builder in the app lets you choose a verification signal directly, because you picking your own metric is an authored choice rather than a model’s guess.
How a day closes
A pending occurrence becomes expired when the next date begins in your current coaching time zone. Manual completion and progress commands are admitted only for the current local date. Delayed offline replay and client clocks cannot backdate them, and there is no grace window.
Record-backed results stay reconcilable, because their owning records carry the
authoritative source date. A late or corrected record re-evaluates the occurrence
against its frozen revision and target, so expired can become completed, and
a record-based completion can return to expired when the criterion no longer
holds. Occurrences you completed, skipped, moved, or withdrew are not touched by
that reconciliation.
Allowances settle only at day close. An at_most mission stores the amount
used, never the amount remaining, so a later target change never rewrites what
the stored progress means. Usage may exceed the target, because clamping it
would hide the evidence that the allowance was broken. And a record-backed
allowance needs positive evidence that its domain was observed that date: no
records cannot be read as zero use.
Edge cases and fallbacks
- Editing a recurring mission starts on the current local date. If the new schedule still includes today, today’s occurrence adopts the new content immediately.
- Changing the verification authority clears the existing answer and its evidence, because they cannot judge the new action.
- A proposal may ask for tomorrow outright (and only that way) when the coach worded a change as beginning tomorrow.
- An edit never rewrites a past date: a revision applies from today forward, and the record-backed reconciliation above is the only thing that can still change a past occurrence.
How to read your score
The Mission ring is the mean completion ratio of the day’s countable occurrences, with the completed count over the countable total at its centre. Allowances are excluded from it: that ring counts actions accomplished, and an open limit would either hold it down all day or shrink it in the evening.
A dash is not a zero. It means the day has nothing countable.
What to do with it
- Keep the countable list short: With three occurrences each is worth a third of the ring; with twelve, none of them means anything.
- Decide on pending proposals rather than letting them queue: Six is the ceiling, so an undecided queue is what stops new suggestions arriving.
- Edit rather than retire and recreate: an edit carries the mission’s history; a new definition starts from nothing.
- Use an allowance for things you want less of (such as “coffee at most two”), and a countable mission for things you want to do. They are judged at opposite ends of the day on purpose.
Troubleshooting & FAQs
- Why did my mission expire when I finished it just after midnight?
- A pending occurrence expires when the next date begins in your coaching time zone, and there is no grace window or past-completion screen. Record-backed missions are the exception: a late or corrected record carries its own authoritative date and can still turn an expired occurrence into a completed one.
- The coach stopped suggesting new missions. Why?
- At most six mission change proposals may be pending at once, across every origin. The ceiling creates back pressure on purpose: a queue of undecided proposals is the real cost to you, so nothing new arrives until you decide something.
- Can the coach change a mission I already have?
- Not on its own. Approval owns every mission mutation. The only two exceptions are narrow and explicit: activating your goal during onboarding creates a bounded starter set, and submitting a Condition Check-In may create at most one AI-authored mission for that same day. Everything else waits for you.