Caffevolve^™

Caffeine Management & Delivery Platform

---

Plan my Day

How It Works

---

OverviewThe Planner Plan CheckVerification

Confidential

information@caffevolvetech.com  ·  October 2026

Plan my Day is an optional tool for planning a whole day of coffee at once. It runs in three stages, and this document covers all of them: the Planner, where the plan is made (Part 1), and Plan Check, which keeps the plan true as the real day unfolds (Part 2).

Both parts run on one engine: the same caffeine model, the same two ceilings and the same Rebalance rule. The Planner is that engine with nothing yet had; Plan Check is the same engine with part of the day already had.

1.1  What the Planner is

Every other path in the platform resolves a single cup in the moment. The Planner works one level up: the user lays out an entire day's drinks in advance and shapes them together until the whole day sits inside their Caffeine Comfort Zone before the first cup is brewed. It is a planning tool, not a brew path: it commits nothing to the device and brews nothing itself. The platform advises; the user decides.

It is a Resident User feature. A plan belongs to a saved profile, draws on that profile's ceilings, decay rate and history, and never appears during a guest brew. The Planner is reached from the Plan my Day button on the profile screen (PS1a), which, like Home and Away, stays disabled until tonight's bedtime is declared.

1.2  The question it answers, and the projection

A single Brew Session recommends the cup that keeps the user inside their Caffeine Comfort Zone right now, but it treats each cup as if it were the last of the day. The Planner asks the whole-day version: how the day's caffeine is spent across every drink planned. A day of caffeine is a budget spent against two boundaries at once.

The Planner projects the whole day, starting from what is already in the user's system, and reads two values from it:

• Wake Hours Peak, the highest point of the curve during the waking day, checked against the Wake Hours Ceiling.
• Bedtime residual, where the curve lands at tonight's declared bedtime, checked against the Bedtime Ceiling.

Every change re-draws the curve and re-reads both values immediately. Because caffeine clears slowly, the day has a clean shape: spend earlier, when there are hours left to clear it, and taper toward evening. A late-afternoon or after-dinner cup becomes a deliberate choice, shown to fit both ceilings before it is brewed.

1.3  Building the day

Each drink is set by time (15-minute steps), place, type and size. What can be tuned follows the device:

• A coffee made on a Caffevolve device, at home or at an equipped office, is tuned by serving size (8, 10, 12, 16 or 20 oz), brew strength (Light, Medium or Strong) and caffeine blend (0–100% in 5% steps), because the device blends caffeinated and decaffeinated beans to order. Strength is set to Auto by default, taken from the sub-profile covering the drink's time, else the profile's; French Press, Pour Over and Cold Brew always brew at Medium.
• A drink from a place without a device (a café, a shop, a workplace counter) is tuned by size, or shot count for espresso.

The profile already records which workplaces are equipped, so the Planner offers the right controls without asking.

1.4  Protect and Rebalance

Protect, the star on each drink, holds a drink exactly as planned while the rest of the day is shaped around it. It is how the user names the cup they will not give up. Up to two drinks can be protected; none is protected by default, so there is always room left to rebalance.

Rebalance (which replaces the retired Fix it for me) adjusts every unprotected drink to bring the day under both ceilings, using the same gradual taper as Plan Check: away drinks size down first, latest first; device cups then share the remaining bedtime room, smoothed so that no cup is cut more than 15 points beyond the cup before it; both ceilings are checked exactly. No drink is ever removed. The result is applied to the plan at once: each changed drink is outlined and carries a back arrow that returns it to its earlier setting, and the user can keep adjusting by hand from there.

When even every unprotected drink at its minimum cannot clear the day, the Planner says so and names what would have to give: unprotecting a drink, moving it earlier, or taking it decaf.

A user who wants most of their caffeine in the morning protects the morning cups or makes small edits; otherwise the taper spreads the cuts across the day.

1.5  Routines and one-off days

A shaped day can be saved as a Routine and set to repeat on any chosen days: every day, weekdays, weekends, or any mix. On a day a Routine covers, it becomes that day's active plan automatically, projected fresh against today's clock and the user's real state before any brewing begins.

Days that don't repeat are handled just as directly. The Planner opens on a front door, not on the Routine. The user can start from a blank day, from today's Routine as an editable copy, from another Routine, or from a recent day. Two commit actions sit side by side:

• This is my plan for today sets a one-off for today only. It takes precedence over the Routine for the rest of that day; the next day the Routine resumes on its own.
• Save as routine saves the day as a recurring Routine.

To pick today's plan, the platform checks today's committed one-off first, then the Routine for today's weekday. A Routine suits the day that repeats, such as a day at the office; a one-off suits the day that doesn't, such as late meetings or an end-of-day push. Delete routine removes a saved Routine but keeps today's drinks.

Edits and Rebalance made during the day, through Plan Check, change today's plan only. The saved Routine is never touched unless the user saves the change from the Planner.

1.6  Starting from the real state

The projection always starts from what is actually in the user's system. Opened mid-day, the Planner folds the drinks already had into a locked baseline drawn from the device log and any logged drinks. Every plan also accounts for what is still in the user's system from the night before, including a plan made the evening ahead.

1.7  Why the Planner depends on the rest of the platform

Planning a day is a solvable problem only once four capabilities exist: a device that blends to order, so each drink is composable rather than a fixed dose; the Caffeine Comfort Zone, whose ceilings give the projection its targets; the personal Caffeine Decay Rate, so two people drinking the same cup are shown landing in different places at bedtime; and a real-time residual picture from device brews and logged drinks, so a plan starts from what is truly in the system. Remove any one and the projection has no target, no accurate curve, or no true starting point.

1.8  Worked example: Diane's workday

Diane: Caffeine Decay Rate 4.5 h, bedtime 11:30 PM, Bedtime Ceiling 75 mg, Wake Hours Ceiling 490 mg. She plans four cups and protects her 11:00 drip. Each cup's strength follows her sub-profiles: the 11:00 falls in AM Focus (Medium) and the 2:15 in PM Deflate (Light); the French press and pour-over always brew at Medium.

If Diane wants her French press at full strength, she protects it as well. Rebalance then takes the 9:45 to 50% and the 2:15 to 60%, landing at 74.9 mg at bedtime with a 364.8 mg peak. All figures were produced by the independent engine with each cup at its resolved strength, and the Caffevolve prototype's Planner gives the same result.

2.1  What Plan Check is for

Plan Check keeps a Plan my Day plan honest: each time a planned cup comes due, it re-solves the rest of the day against what the user has actually had and shows whether the day still lands under both ceilings.

A plan is a forecast made in advance. The real day drifts: an extra cup, a café stop, a changed time. The notice closes that gap one cup at a time, at the moment it matters, instead of leaving the user to discover a bad night after the fact.

What it is meant to accomplish:

• Show the cup planned for now, with its size, blend and caffeine, where every device brew begins (the Make a Drink screen).
• Re-solve the whole remaining day, not just the cup in hand. Cups already had are frozen as actuals; every cup still to come is recomputed.
• Honor both ceilings: the Bedtime Ceiling (residual at bedtime) and the Wake Hours Ceiling (peak during the day).
• Offer one clear next step for the day's state: nothing when on plan, Rebalance when over, Brew when adjusted.
• Stay advisory. The system recommends, the user decides, the machine always brews. Nothing is changed without a tap.

Every rule described here has been verified case by case against an independently built engine and against the published figures in the Blend Calculation Reference (Appendix).

2.2  Diane's test day

The examples in Part 2 use one of Diane's workdays, with every cup at Medium strength. She has almost no bedtime room on this day, so nearly any unplanned caffeine pushes her over.

2.3  How the day is re-checked

Every change re-projects the whole day: every edit to a time, size or blend, every protect, every logged drink and every brew. Drinks already had are fixed as they were actually had; every planned drink still to come is recomputed, and both ceilings are checked. The day is always re-solved whole, never one cup at a time.

Rebalance for me follows the rule described in 1.4: drinks from places without a device size down first, the latest first, and device cups then share the remaining room in a gentle taper, so earlier cups keep more of their caffeine and the afternoon steps down gradually. Before offering Rebalance, Plan Check confirms that some rebalance can clear the day. When none can, because drinks already had or protected drinks hold too much caffeine, it says so instead of offering the button.

2.4  UX flow — the notice

The notice appears once, on the Make a Drink screen, and always offers exactly one next step for the state the day is in.

When it appears. A plan is active for a Resident User, and the user opens Make a Drink with a planned cup due within about 90 minutes. Make a Drink feeds every device brew path (BrewNow!, QuickBrew, Fresh Grounds Only), so the notice shows there and is not repeated on the screens that follow.

What it always shows, collapsed:

• "Planned for right now" and a View plan link that opens the rest of the day.
• The cup: drink, blend and caffeine ("Your Drip / Filter — 40% caf, ~64 mg"), then time, place, size and blend.
• A bedtime pill ("At bedtime 73 mg"), a peak pill only when the peak is over, and a status pill.

What it offers, by state:

The brew buttons appear only on a changed cup that is back under both ceilings; an over-ceiling day always goes through the revision first.

The two brew actions:

• Brew this cup goes straight to BrewNow!'s Hold to Brew with the revised size and blend loaded. The hold gesture is the confirmation. For a planned French Press or Pour-Over it reads Grind for this cup, since the device only grinds.
• Confirm & Brew opens the full picture (PS6-A): final blend, strength, additives and any open sub-profile window, all editable before hold-to-brew.

Why no brew button when on plan or over. On plan, the normal paths already deliver the planned cup. Over a ceiling, a one-tap brew would brew the cup that no longer fits; the revision comes first. The user can always brew anything through the normal paths.

After a brew, the cup becomes an actual, the clock moves on, and the next planned cup's notice takes over. After the last planned cup, the notice reads "Day complete" with the final bedtime figure.

2.5  UX flow — the expanded day

View plan opens every cup still to come as an editable card; each change re-solves the day at once. It is forward-looking only: cups already had are not listed.

Each drink card:

Below the cards: + Add a drink (15-minute time slots from now to bedtime, device or away), then the two ceiling figures side by side: projected bedtime residual against the 75 mg ceiling and wake-hours peak against the 490 mg ceiling, each green or red. A short note underneath says either "You're under both ceilings" or points to Rebalance.

What "plan" means for the back arrow. Tapping Brew saves the rest of the day as the new plan. The arrow then returns a card to where it stood at the last brew, not to the morning plan. Rationale: once the user brews, the settings they chose for later cups are what they agreed to, so the arrow never surprises them. The morning plan is still one step away through Reset this day or Start over.

Useful side effect. After Rebalance, the arrow lights up on every cup that Rebalance changed, so the user can see what moved and undo it one cup at a time. Undoing may put the day back over a ceiling; the pills turn red again and Rebalance returns.

Brew confirmation. A short confirmation spells out the full brew: "Brewed — Drip / Filter · 12 oz · 70% caf · 112 mg".

2.6  The real day: matching brews, missed cups, bedtime

The plan meets the real day through five rules. Each cup on the plan is in one of six states: planned (still to come, adjustable), brewed, missed (its window closed unbrewed; still counted), had elsewhere, skipped (removed by the user's answer) or dropped (removed automatically when cups in a row are missed). Unplanned brews and logged drinks are extras.

1. A brew within 90 minutes of a planned cup is that cup. Before or after. If two windows overlap (Diane's 9:45 and 11:00 are 75 minutes apart), it is the nearest unbrewed cup; on a tie, the earlier one. Each planned cup is matched once. The brew replaces the cup at its actual time with its actual size and blend, and the day re-solves.
2. Outside every open window, Make a Drink asks: "Does this replace a planned drink, or is it an extra?" The buttons list up to three unbrewed cups, nearest first, with missed ones marked "not brewed," plus "It's an extra." Replacing swaps the cup; an extra is added and gets the pre-brew warning if it would push the day over. With no unbrewed cups left, a brew is an extra without asking.
3. An away drink logged in CaffevolveGo (ECE) matches any planned cup the same way, device or away. A café drip logged at 11:30 inside the window of a planned 11:00 device cup is that cup: it replaces it at the logged dose, so the day is not charged for both. Outside every window, the same replace-or-extra question is asked, before the drink is saved, whether it is logged as Something Else or through the Offsite Advisory. The Offsite Advisory confirm screen also shows Plan Check for the drink being ordered, using the café drink's caffeine.
4. A single missed cup keeps counting as had until the user says otherwise. This is the safe assumption: dropping a cup she actually had would let Rebalance overshoot her ceiling. At the next interaction that isn't a brew, the app asks "Your 11:00 Drip wasn't brewed. What happened?" Had it somewhere else keeps it counted; Skipped it removes it and returns its room to the day. If the next action is a brew outside every window, the replace question covers it instead.
5. When more than one planned cup in a row is missed, the earlier ones are dropped automatically. Only the most recent missed cup stays (counted until answered, as in rule 4). A run of missed cups means the plan has slipped; and because away drinks are logged in CaffevolveGo and matched by rule 3, a cup that passed with nothing brewed or logged most likely wasn't had. A brewed or logged cup between two missed ones breaks the run; extras do not. The one blind spot, caffeine had away and never logged, is a platform-wide limit, not specific to Plan Check.
6. A bedtime declared differently mid-day re-solves the whole day at once. Later bedtimes free room; earlier ones may turn Plan Check red with Rebalance offered. What remains from last night is unchanged.

Plan Check's notice shows the planned cup due within 90 minutes of now; when none is due, it shows the next planned cup without brew buttons.

a 1:00 PM brew inside the 2:15 window is matched to the 2:15 automatically while the 11:00 sits missed. Because the 11:00 is a single miss, it stays counted until Diane answers, so if she skipped it the error is on the safe side and one tap corrects it. Rule 5 covers the case where several cups in a row pass.

2.7  Unplanned drinks

Warn before an unplanned drink is committed to wherever possible; fall back to a notice at logging when it was not. The effect on the plan is the same however the drink enters the record.

The rule. Any unplanned drink that puts the day over a ceiling while planned cups remain later in the day triggers one simple notice: "Your plan needs revision to stay under your ceilings." No projected figures and no named cup; the adjusted view comes with the next planned cup's notice.

At the next planned cup. The Plan Check notice opens red with Rebalance for me offered, never applied automatically.

When it matters. Only when the drink uses up more room than the plan left under either ceiling. Room is spent very differently under each:

• Bedtime: early drinks barely register; most of a morning drink has cleared by the time Diane goes to bed.
• Peak: a drink shortly before the day's peak adds nearly its full dose to it.

Plan my Day tends to produce plans that finish just under the Bedtime Ceiling, because the fix lands the day right at the limit, so many users will run Diane's thin margin.

ECEp's role. The ECEp check-in looks backward: it asks for drinks already had but not logged, in two 6-hour windows per wake cycle. Window 1 matters to a plan only if the plan was made the previous day or came from a saved Routine. Window 2 can affect any plan, including one made that morning.

All 66 test scenarios across five profiles, including 17 day-event sequences, give the same result in the Plan Check model and in an independently built engine, and both reproduce the Blend Calculation Reference's published figures to within its own rounding.

A.1  How it was checked

1. Shared test fixtures. Five profiles, each with a planned day, run through the same nine scenario types (45 cases), plus a peak-limited case and three required Rebalance checks (49 in all). Re-run after Rebalance changed to the gradual taper (15-point step) on October 1.
2. Independent engine. A second engine was written independently in Python from a written specification only, without access to the model's code.
3. External reference. Both engines were checked against the published numbers in the Blend Calculation Reference v50 (Parts Four, Five and Seven), and against hand arithmetic for two days.
4. Comparison. Bedtime residual, peak, state, solvability and every Rebalance output compared case by case; any difference was traced to its cause and fixed before re-running.