Tasks
Google Calendar gives you a date and a repeat interval. Casabeza gives you the full range of scheduling logic that home maintenance actually requires — seasonal, astronomical, completion-anchored, and inventory-triggered.
Google Calendar is excellent at what it does. It schedules meetings. It handles human coordination across time zones. It answers the question: when should we all be in the same place?
Home maintenance doesn't have those requirements. The boiler service doesn't need a conference link. The gutters don't care about attendee availability. What home tasks need is scheduling logic that reflects how domestic work actually accrues — and that logic is much richer than "every Thursday at 9am."
A calendar gives you a date and an interval. Casabeza gives you a scheduling model that matches the actual rhythms of a property.
The basics are fully covered. Daily, weekly, fortnightly, monthly, bimonthly, quarterly, yearly — and a custom cadence mode where you specify any number of days. If a task needs to happen every 47 days, it can.
Within fixed intervals, you can pin notifications to specific weekdays. A task that falls due on a Wednesday can be held until Friday if that's when you do house admin. The scheduled date remains accurate — what moves is only the notification, so your record of when the task was due isn't distorted by convenience.
This is where calendar-style scheduling breaks down most visibly.
A filter change on a repeat every 90 days, calendar-anchored, will drift. You change the filter on day 85 because you happen to be near the cupboard. The calendar next fires on day 90 from the original date, not from when you actually did it — so your next reminder arrives in five days rather than three months.
Casabeza lets each task declare what its next occurrence should be anchored to:
The choice between these is a genuine design decision per task. A safety inspection probably wants schedule-anchored recurrence so that intervals don't compress over time. A maintenance task that responds to actual wear probably wants completion-anchored recurrence so the interval reflects real elapsed time.
Some tasks belong to a season, not a date. Checking outdoor pipes before first frost, servicing the air conditioning before summer, inspecting the roof after autumn. Attaching these to a fixed calendar date is a fiction — the date that matters is the onset of the relevant season, and that shifts year to year and hemisphere to hemisphere.
Casabeza has native season types for both hemispheres. A task scheduled for autumn in the southern hemisphere fires on southern hemisphere autumn, not a calendar date reverse-engineered from the northern calendar. The hemisphere is a property of the location, not a manual configuration per task.
For tasks tied more precisely to the year's natural pivot points, scheduling can be set to the actual vernal or autumnal equinox, or the summer or winter solstice.
These aren't approximations. The equinox that fires the task is the equinox, calculated for the year in question. If you have garden tasks, orchard tasks, or any maintenance that tracks the solar calendar rather than the administrative one, this is the right anchor.
The standard four-season model is a simplification that most of the world uses for administrative convenience. Ecologically, the year has more structure than that.
Casabeza supports a six-part ecological calendar: prevernal (late winter into early spring), vernal (spring proper), estival (early summer), serotinal (late summer), autumnal (autumn), and hibernal (winter). These divisions track the phenological year — the one that actually governs when plants flower, when pests emerge, when ground conditions change.
For property maintenance and garden tasks, the ecological calendar is often more meaningful than the administrative one. "Inspect drainage" belongs to a different season than "apply lawn treatment," and the six-part model captures that distinction without requiring manual date management.
Some tasks track the lunar cycle. Garden tasks — particularly planting, pruning, and soil work — have traditions of lunar timing that many people actively follow. A task can be scheduled to fire on the next full moon, new moon, first quarter, or last quarter.
This isn't ornamental. It's the same scheduling infrastructure used for intervals and seasons, applied to the lunar calendar. If you want to be reminded to do something at a specific phase of the moon, the system handles it the same way it handles everything else.
Some tasks don't belong on any calendar. They belong to a condition.
When a stock level falls below a threshold, that's when restocking becomes a task — not on a fixed date, and not after a fixed interval, but when the quantity warrants it. Casabeza can trigger tasks from inventory state: a task fires when a tracked item's quantity drops under a defined level, or rises over one.
This changes the model for consumables management. You don't need to estimate how often you use something and set a reminder to match — you track the quantity, set the threshold that matters, and let the system decide when the task is due based on what's actually in the cupboard.
Bills share the same scheduling infrastructure as tasks. A bill payment can be set to quarterly, to a fixed date each month, to a custom cadence, or to any of the same schedule types available to maintenance tasks. The logic is consistent across the system, not bolted on differently per feature.
Google Calendar is not a home management system. It's a meeting coordination tool that many people press into service because nothing better was available. Casabeza is built around the question of what a home actually requires — and the answer turns out to involve seasons, moons, thresholds, and elapsed time, not just dates on a grid.