Most scheduling tools put items on a timeline. You pick the task, you pick the time, you drag it into place. Dependency-based scheduling works the other way around: you describe what needs to happen, and the system figures out when.
The core idea
Actions have prerequisites. Cooking dinner requires ingredients. Having ingredients requires a grocery trip. The grocery trip requires a free hour and enough money in the budget. These prerequisites form a chain, and the schedule resolves that chain automatically.
This is the same principle behind critical path scheduling in project management. Construction teams have used it for decades: you can’t install windows before the walls are up, and you can’t put up walls before the foundation is poured. The schedule flows from the dependencies, not from someone manually assigning dates.
Dependency-based scheduling applies that logic to daily life. The dependencies are different (groceries instead of concrete, energy instead of crane availability), but the mechanics are the same.
How it works in practice
Say you want to cook three dinners this week: pasta on Monday, stir fry on Wednesday, and soup on Friday.
A traditional approach: you decide to cook on those days, add them to your calendar, write a grocery list, check your budget, pick a time to shop, and hope everything lines up.
A dependency-based approach: you tell the system what you want to eat. The system checks what ingredients you have, identifies what’s missing, estimates the cost, finds a time for the shopping trip that fits your schedule and budget, and slots the cooking sessions into evenings where you’ll have enough time and energy.
If something changes mid-week (you work late Wednesday and can’t cook), the system moves the stir fry to Thursday, checks whether that affects Friday’s plan, and adjusts the grocery list if Thursday’s new timing changes what you can realistically make.
You don’t rearrange anything. The system already knows what depends on what.
Resources and transactions
Dependency-based scheduling needs a richer model than tasks and dates. It needs to understand what things cost, what they produce, and what they require.
In Monoceph, this model is built on two concepts:
Resources are anything you have, need, or produce. Money in your checking account. Hours in your evening. Eggs in the fridge. Energy after a full workday. PTO days. Shelf space. Each resource has a quantity that changes over time.
Transactions are actions that consume and produce resources. Grocery shopping consumes time and money, and produces food. Cooking consumes ingredients, time, and energy, and produces a meal. Working consumes time and energy, and produces income.
Dependencies emerge naturally from this model. If a transaction requires a resource you don’t have enough of, the system looks for another transaction that produces it, and schedules that one first. Cooking needs eggs. You’re out of eggs. A shopping trip produces eggs. The shopping trip gets scheduled before the cooking.
Forward planning
One advantage of dependency-based scheduling is that it plans ahead, not reactively.
If you tell the system you want to cook a specific recipe next Friday, it doesn’t wait until Thursday to figure out you’re missing an ingredient. It looks at Friday’s requirements now, traces the dependency chain backward, and schedules the prerequisite steps (shopping, defrosting, prep) at the right times earlier in the week.
This forward-looking behavior extends beyond meals. If your rent is due on the first of the month and your paycheck arrives on the 28th, the system understands the cash flow constraint and plans other spending around it. If you have a deadline on Thursday, the system can work backward from the deadline and schedule preparation steps across the days before it.
The result is a schedule that anticipates what you’ll need, not one that reacts after you’ve noticed a gap.
Handling changes
Plans change. Dependency-based scheduling handles this better than manual scheduling because the relationships between items are explicit.
When you manually schedule your week and something shifts, you have to trace the consequences yourself. “If I can’t shop on Tuesday, that means I can’t cook on Wednesday, which means I need takeout, which means I’ll spend more, which means…” You’re resolving the dependency chain in your head.
In a dependency-based system, the chain is already mapped. Move one item, and everything downstream adjusts. Cancel the grocery trip, and the meals that depended on it get rescheduled or flagged. Spend more than expected on something, and tasks that depend on that budget get shifted.
This isn’t about removing your control. You still decide what matters and what you want your week to look like. The system handles the logistics of making it work.
Dependency-based scheduling in Monoceph
Monoceph applies dependency-based scheduling to your entire life, not a single project. You describe your resources (income, time, energy, food, commitments) and the transactions that connect them. Monoceph resolves the dependencies and generates a schedule.
When you add a new goal, change a commitment, or encounter the unexpected, the schedule adapts. You don’t rebuild the plan manually. Monoceph already knows the structure.
Monoceph is free during early access at monoceph.co.
