Every plan is honest
for about a day.
Planner keeps listening.
The planning engine I run my own week on. It turns capacity, protected time, placement rules, and a live work queue into a calendar that can be re-planned without hiding the consequences.
The job.
Planner keeps a live model of what the week can hold and what the work requires. It does not confuse an empty calendar cell with capacity, and it does not treat Monday's arrangement as a promise that reality has to keep.
The queue can be fed from whatever already carries the work. Planner applies capacity and placement rules, protects the time that must not be offered away, and projects the result onto the calendar.
The decisions behind the engine.
Capacity comes before placement.
A task does not earn a place because there is white space on the calendar. Planner first asks whether the week has the hours, attention, prerequisites, and working conditions the task needs.
Protected time is unavailable to inbound demand.
Time held for delivery, recovery, or work on either side of a commitment stays protected. The booking layer reads that boundary and never publishes those hours as open slots.
Re-routing starts from the changed fact.
A longer call, a new blocker, or an urgent item changes the feasible week. Planner calculates from the new state and shows the chain of consequences: what moves, what becomes late, what is displaced, and what no longer fits.
The calendar is a projection, not a second source of truth.
The work queue carries the commitments and dependencies. The calendar shows the current arrangement. When the plan changes, that projection changes with it instead of drifting into a competing version of the week.
Dry-run first, everywhere.
Every command prints what it would change and writes nothing until told. A re-plan is a diff before it is an action. You see the movements, conflicts, and dropped assumptions, then decide whether to commit them.
That gate is part of the engine, not a temporary safeguard. The engine calculates. The operator judges.
The operating stack.
The engine behind the other two.
Capacity-aware booking captures demand and turns a confirmed slot into a new commitment. Planner absorbs it and proposes the changed week. Scheduling ops is the managed offer: I operate the same loop and keep the queue and calendar aligned as reality moves.
Each stands alone. Together, an inbound booking rearranges the proposed week before the operator has read the email. The booking confirms automatically; the calendar re-routing still waits for the operator.
Licensing this engine
Planner is licensed for the client to operate. Your capacity model, protected time, queue sources, placement rules, and calendar projection are set up around your work, then the controls stay with you.
Who it suits - An operator who wants the planning system in-house and wants every state-changing command to stop at a visible gate.
What it replaces - A task list that ignores capacity, a calendar that drifts away from it, and manual re-planning whenever the week breaks.
The proof today - I run my own week on Planner. Its booking layer replaced Acuity on this site. That is the claim: my operating week and a live booking flow, not an invented client base.
This engine changes as I run it; if something here has gone stale, tell me and I will fix it.