Aestus-native

The standup your board already wrote

Every weekday morning, one post of what moved, who is blocked and what needs a decision — read from your own records, every line openable.

Join the waitlist See what it produces

Async standup

Write the async standup

Who it is for: Teams who run a daily standup and have noticed the status half is a database read done by people.
What starts it: Weekdays at 09:00 in your workspace's time zone, one post per team; On a schedule

Turn it on in Aestus

A standup meeting exists because nobody can see the board. Fifteen minutes, every weekday, for a whole team, spent reading out state a database already holds — and half of it is wrong, because people report from memory.

Aestus already records the column moves, the runs, the pull requests, the dependencies and the agent sessions. This use case turns that record into one post, every weekday morning, in the channel the team already reads: what moved, who is waiting on whom, what needs a decision today and from whom, what the agents did and what it cost, and what has not moved at all. Every line carries a source you can open.

What makes it worth reading is where the numbers come from. Every count — how many cards moved, how many are blocked, how long something has waited — is computed from the records before the model is asked to write anything, and recomputed from the same records afterwards. The model's own arithmetic is discarded. "Waiting too long" is not a number this use case chose either: it asks the same shared rule the rest of the product uses, so a card that is overdue in the standup is overdue everywhere else too.

It reports the quiet half as well. Work nobody mentioned in a meeting is work nobody answered about, and the tickets that have not moved for two weeks are exactly the ones a round of updates never reaches. They get their own section, with how long, and no guess about why.

It changes nothing. The model that writes the standup has no tools; the only thing that leaves Aestus is one message to one channel you choose, behind the same approval step every external send goes through. With no channel connected it still runs, and the document and the notification land in Aestus.

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

Daily standup — Northwind Platform · Friday 11 Sep 2026

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

Needs a decision today: The auth provider for the partner portal: NW-412 has been in Approval for three working days waiting on Dana Reyes, and NW-418 and NW-421 cannot start until it clears. Three working days is the shared staleness rule's answer, not a model's — it counts whole weekdays, so a weekend does not make a card look ignored.
Blocked: NW-418 and NW-421 wait on the auth decision. NW-407 came back to Todo after run LIORHEBE-RUN-1182 failed checks_failed and nobody picked it up. The failure code is copied from the run record; the standup never turns a failure into a cause.
People: One block each for Dana Reyes, Tom Okafor and Priya Nair: what each moved, and what is waiting on them. Nobody is graded, praised or blamed — the review step rejects a line that guesses at why someone did something.
Agents: The coding agent: 3 runs, 2 accepted, 1 failed, $2.14. Claude Code has held NW-388 since 02:00 and has not reported for 31 hours, so it is shown as stalled rather than as working.
Quiet: Three cards nobody has touched for weeks, with how long each has been silent. This is the half a round of verbal updates never reaches, because nobody answers about the ticket they forgot.
What shipped: NW-392, NW-394 and NW-396 reached a terminal column inside the window. Shipping means the board says so, not that a branch merged.
Sources: Nineteen numbered rows: the audit event, run, ticket or artifact behind every line above. Sources is the one section that is printed even when every other section is empty.

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

01It reads the window
Everything that happened since yesterday morning: column moves, runs, pull requests, dependency changes, agent sessions. Monday covers the weekend too.
02It writes the standup
Sections for the decisions that need someone today, what is blocked and on whom, one block per person, one block per agent, what has gone quiet, and what shipped.
03It checks itself before anyone sees it
A review step compares every id, count, cost and date against the records it read. If a value is not in the records, the standup does not go out.
04It posts once and files the document
One message in your channel, one document on the standup ticket, one notification. No ticket is changed.

By hand, and on Aestus

The same job, on either side.

By hand
Each person recalls yesterday and types it.
On Aestus
Read from column moves, runs and pull requests.
By hand
Fifteen minutes each, every weekday.
On Aestus
Nobody writes anything.
By hand
You take someone's word for it.
On Aestus
Every line names a record you can open.
By hand
Work nobody mentioned stays invisible.
On Aestus
Reported as quiet, with how long it has been.
By hand
Agents on the team are absent from the round.
On Aestus
One line each: what moved, what failed, what it cost, what it waits on.
By hand
Counts are read out from memory.
On Aestus
Every count is recomputed from the records, never written by a model.

What Aestus records

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

The run
Cost, tokens, latency and whether the review step passed, on the same ledger as every other run in the workspace.
The document
Each morning's standup is a document on the team's standing standup ticket, with its own revision history.
The window it read
The run records the scope, the window and the number of moves it saw, so a standup can be checked against the ground it covered.

What it connects to

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

slackOptional

Questions teams ask

Does it change any of our tickets?

No. It reads the board and writes a document. It never files, moves, assigns or closes anything, and the model that writes it has no tools at all.

What happens on a day when nothing moved?

It says so, in one line, and stops. You can also tell it to stay silent on quiet days.

Can it be wrong?

Every count is computed from the records before the model sees them, and recomputed afterwards against the same records. A review step checks every id, cost and date too. If a value is not in the records, the run fails and nothing goes out.

Does it grade people?

No. It reports what moved and how long something has waited. The review step rejects a line that praises, blames or guesses at why.

What about agents?

They get the same treatment as people: what they moved, what failed and with which error, what it cost, and what they are waiting on. An agent that has stopped reporting is shown as stalled, never as working.

All use cases How access is governed

Sources

docs/runbooks/use-case-workflows.md

Hand over Write the async standup.

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

Talk to us

Questions teams ask

Does it change any of our tickets?

No. It reads the board and writes a document. It never files, moves, assigns or closes anything, and the model that writes it has no tools at all.

What happens on a day when nothing moved?

It says so, in one line, and stops. You can also tell it to stay silent on quiet days.

Can it be wrong?

Does it grade people?

No. It reports what moved and how long something has waited. The review step rejects a line that praises, blames or guesses at why.

What about agents?

Sources

docs/runbooks/use-case-workflows.md

The standup your board already wrote

Write the async standup

What you get

Daily standup — Northwind Platform · Friday 11 Sep 2026

How it runs

By hand, and on Aestus

What Aestus records

The run

The document

The window it read

What it connects to

Questions teams ask

Other use cases

Hand over Write the async standup.

The standup your board already wrote

Write the async standup

What you get

Daily standup — Northwind Platform · Friday 11 Sep 2026

How it runs

By hand, and on Aestus

What Aestus records

The run

The document

The window it read

What it connects to

Questions teams ask

Other use cases

Hand over Write the async standup.