Everyday productivity

The week you can actually finish

Monday morning, Aestus subtracts the hours already booked in your calendar from the hours you have, and says what fits and what does not.

Join the waitlist See what it produces

Every Monday

Plan your week

Who it is for: Anyone who plans a week by hand on Monday and finds by Wednesday that the plan never had room in it.
What starts it: A schedule you choose — Monday 07:00 in your workspace's time zone by default; On a schedule

Turn it on in Aestus

Monday morning goes the same way everywhere. Calendar, inbox, chat, board, and then a guess about what will fit. The guess is wrong, and it is wrong in one specific way: almost nobody subtracts the hours already booked before committing to the work. A week with fourteen hours of meetings in it is not a forty-hour week, and a plan that does not say so is a to-do list with a date on top.

So the subtraction is the point, and it is the second thing on the page. Working hours, minus the meetings already in the calendar, minus the focus blocks already held. Every one of those numbers names where it came from — a count of calendar events, a count of tickets, or the working-hours figure you set — and every meeting's hours are its own start and end times rather than a duration anybody estimated.

The other half is what does not fit. A plan that lists everything has decided nothing, so the commitments are selected against the hours that are actually left, in a fixed order: a ticket that stops somebody else, then one due inside the week, then higher priority, then whatever has already waited longest on the same staleness rule the rest of Aestus uses. Items are taken in that order until the next one would not fit, and then it stops — it does not shuffle to find a smaller ticket that would round the total up. Everything left over is named with the rule that lost it, because "it did not fit" is not something a reader can argue with.

The number a plan must never get wrong is the one it does not have. If the calendar could not be read — no connection, a revoked scope — then the booked hours are unknown, and a plan that treated that as an empty calendar would quietly assume a free week while looking exactly as authoritative as a correct one. Instead it publishes no hours at all, commits nothing, and says which source it could not read. A plan that is visibly incomplete is recoverable; a plan that is invisibly wrong is not.

Nothing is priced that nobody sized. Hours come only from an estimate already written on the ticket, so a ticket without one is excluded from every total and named as excluded rather than counted as free. The same discipline runs through the rest: a review step recomputes every total before the document is written, and a plan whose arithmetic does not hold is not published at all.

It is a personal answer, so it contains only what one reader may see. Every read is made as that person: a ticket owned by a team they are not on is dropped entirely — never shown with a placeholder — and counted in a number the document prints. Who the plan is for comes from the run itself and cannot be supplied as a setting, so asking for somebody else's week is refused rather than quietly honoured.

Then it ends in work rather than prose. The priorities and due dates it named are set, an ask that had no ticket gets one, and the plan lists exactly what it changed. It never moves a card between columns, never touches a calendar event, and never sends a message — and it says all three, in its own words, at the bottom of every plan it writes.

What you get

The artifact this use case produces, in the product view you would read it in.

Example — fictional team and data. Not a live run or customer result.

Worked example

document

Week of 2026-09-14 — Priya Raman

Produced by: Run NW-RUN-4120 · read-only calendar · document artifact · demo values

The week in one line: 14.5 hours of meetings are already booked and 21.5 working hours are left. 4 commitments fit and 4 do not, and every one that does not says which rule lost it.
Capacity: The subtraction nobody does by hand, with a source on every row: 40 working hours, minus 14.5 hours of meetings, minus 4 hours of focus blocks already held, leaves 21.5. The week is asked for 28, so the shortfall is -6.5. Every figure is recomputed from the rows before the document is published, and a plan whose arithmetic does not hold is not published at all.
Do these: 4 items, 21 hours of the 21.5 available. LIORHEBE-1904 is first because it blocks LIORHEBE-1911, LIORHEBE-1912, and due 2026-09-16 inside the week, and priority 4, and aging on the shared wait ladder. The order is fixed — what blocks somebody else, then what is due inside the week, then priority, then what has waited longest — so the same board always produces the same plan.
What slips: 4 items, each carrying the rule that lost it: [no capacity was proved, so nothing was committed], [nobody sized it, so it is in no total], [the week ran out of hours before it]. LIORHEBE-1893 is here because the week ran out of hours before it, not because anybody judged it unimportant. A ticket nobody sized is in no total at all and is named as excluded.
Asks waiting on you: 3 messages still waiting for a reply, each quoted rather than paraphrased and each pointed at the ticket it belongs to — @dana on 2026-09-11: "can you review the retry PR before Monday". An ask with no ticket behind it gets one filed.
Meetings worth a second look: The booked hours worth a second look, with their attendee counts — "Weekly platform sync" holds 9 people for 1.5 hours. It is a list, not a recommendation: the plan never moves, declines or creates an event.
What I changed on the board: Only priorities, due dates, and a ticket filed for an ask that had none — and only after you see the exact list and choose Apply. The section lists what the board accepted, and apart from it what it did not and why. A column move is the person's decision, and a plan that proposes one is refused rather than published.
What I did not do: The gaps, stated rather than hidden: no calendar event was moved, declined or created and no message was sent; 2 tickets carry no estimate and are in no total; and 2 tickets are on a team this reader is not a member of, so they were left out entirely rather than shown without their team.

How it runs

Each step is one node in the workflow graph the interpreter runs. Nothing here is a prompt chain hidden in a route handler.

Workflow steps

01A schedule fires
Monday 07:00 in your time zone, or whatever you choose. You can also run it by hand when the week changes shape.
02Your board is read before the model starts
Your own tickets, read as you: their priority, their due date, what they block, how long they have been waiting, and the estimate somebody wrote on them. A ticket on a team you are not on is left out entirely and counted.
03It reads the week around you
Calendar events, inbox and chat, as one ledger with a source on every row. A meeting's hours are its own start and end times; nothing is estimated.
04It checks the ledger
A review step rejects any row whose hours do not match the event, any ticket id your board does not carry, and any estimate nobody wrote. One repair attempt, then the run fails rather than publish.
05It does the arithmetic and fills the week
Your working hours minus the meetings minus the focus blocks you already hold. Then it takes commitments in a fixed order until the next one would not fit, and stops.
06It writes the plan and the board
One document with the subtraction at the top, plus the priority and due-date changes it listed. It files a ticket for an ask that had none. Nothing else.

By hand, and on Aestus

The same job, on either side.

By hand
You read four places and hold the total in your head.
On Aestus
One ledger, one document, every row naming where its number came from.
By hand
Nobody subtracts the booked meeting hours before committing.
On Aestus
The subtraction is the second thing on the page, above the list of work.
By hand
A plan built by a chatbot can quietly invent an estimate and look right doing it.
On Aestus
A ticket nobody sized is left out of every total and named as left out. The plan would rather be short than invent a number.
By hand
"What slipped" lives in memory, so the same item slips silently for a month.
On Aestus
Everything that does not fit is named with the rule that lost it, and a third week in a row is recorded.
By hand
The plan and the board drift apart by Wednesday.
On Aestus
The run sets the priorities and due dates it named, and lists exactly what it changed.
By hand
No record of what it read, what it cost, or what it touched.
On Aestus
One run row with cost, tokens, duration and every tool call it made.

What Aestus records

Every run is auditable after the fact, which is what makes handing the job over survivable.

The run
Cost, tokens, duration and whether both review steps passed, on the same ledger as every other run in the workspace.
The plan
Each week's plan is a document on that week's own ticket, so last week's sits beside this one and you can see on Tuesday what you already decided to drop.
What it left out
The run records how many of your tickets were on teams you cannot see, so a short plan can be told apart from a broken one.

What it connects to

Only the tools this workflow actually uses. Each one has a setup guide.

Questions teams ask

Will it move my meetings?

No. It reads the calendar with read-only scopes. It never creates, changes, moves or declines an event, and every plan it writes says so.

What if a ticket has no estimate?

It is left out of every total and named as left out. The plan would rather be short than price work nobody sized.

What happens if it cannot read my calendar?

It publishes no hours at all and says which source it could not read. Treating an unread calendar as an empty one would produce a plan that assumed a free week and looked exactly as authoritative as a correct one.

Who decides what does not fit?

A fixed order, applied in code: a ticket that blocks another one, then a due date inside the week, then priority, then how long it has already waited. Every item that loses says which of those rules lost it.

Can it change my board?

It sets the priorities and due dates it listed, and files a ticket for an ask that had none. It never moves a card between columns, and it never sends a message.

All use cases How access is governed

Sources

docs/runbooks/use-case-workflows.md

Hand over Plan your week.

Tell us how your team does this today and we will set it up with you.

Talk to us

Week of 2026-09-14 — Priya Raman

Produced by: Run NW-RUN-4120 · read-only calendar · document artifact · demo values

The week in one line: 14.5 hours of meetings are already booked and 21.5 working hours are left. 4 commitments fit and 4 do not, and every one that does not says which rule lost it.
Capacity: The subtraction nobody does by hand, with a source on every row: 40 working hours, minus 14.5 hours of meetings, minus 4 hours of focus blocks already held, leaves 21.5. The week is asked for 28, so the shortfall is -6.5. Every figure is recomputed from the rows before the document is published, and a plan whose arithmetic does not hold is not published at all.
Do these: 4 items, 21 hours of the 21.5 available. LIORHEBE-1904 is first because it blocks LIORHEBE-1911, LIORHEBE-1912, and due 2026-09-16 inside the week, and priority 4, and aging on the shared wait ladder. The order is fixed — what blocks somebody else, then what is due inside the week, then priority, then what has waited longest — so the same board always produces the same plan.
What slips: 4 items, each carrying the rule that lost it: [no capacity was proved, so nothing was committed], [nobody sized it, so it is in no total], [the week ran out of hours before it]. LIORHEBE-1893 is here because the week ran out of hours before it, not because anybody judged it unimportant. A ticket nobody sized is in no total at all and is named as excluded.
Asks waiting on you: 3 messages still waiting for a reply, each quoted rather than paraphrased and each pointed at the ticket it belongs to — @dana on 2026-09-11: "can you review the retry PR before Monday". An ask with no ticket behind it gets one filed.
Meetings worth a second look: The booked hours worth a second look, with their attendee counts — "Weekly platform sync" holds 9 people for 1.5 hours. It is a list, not a recommendation: the plan never moves, declines or creates an event.
What I changed on the board: Only priorities, due dates, and a ticket filed for an ask that had none — and only after you see the exact list and choose Apply. The section lists what the board accepted, and apart from it what it did not and why. A column move is the person's decision, and a plan that proposes one is refused rather than published.
What I did not do: The gaps, stated rather than hidden: no calendar event was moved, declined or created and no message was sent; 2 tickets carry no estimate and are in no total; and 2 tickets are on a team this reader is not a member of, so they were left out entirely rather than shown without their team.

Questions teams ask

Will it move my meetings?

No. It reads the calendar with read-only scopes. It never creates, changes, moves or declines an event, and every plan it writes says so.

What if a ticket has no estimate?

It is left out of every total and named as left out. The plan would rather be short than price work nobody sized.

What happens if it cannot read my calendar?

Who decides what does not fit?

Can it change my board?

It sets the priorities and due dates it listed, and files a ticket for an ask that had none. It never moves a card between columns, and it never sends a message.

Sources

docs/runbooks/use-case-workflows.md

The week you can actually finish

Plan your week

What you get

Week of 2026-09-14 — Priya Raman

How it runs

By hand, and on Aestus

What Aestus records

The run

The plan

What it left out

What it connects to

Questions teams ask

Other use cases

Hand over Plan your week.

The week you can actually finish

Plan your week

What you get

Week of 2026-09-14 — Priya Raman

How it runs

By hand, and on Aestus

What Aestus records

The run

The plan

What it left out

What it connects to

Questions teams ask

Other use cases

Hand over Plan your week.