The control plane sits between intent and action. Every drafted message, every external call, every state change is staged as an approval object — with reasoning, sources, and side effects attached.
Three actions. Approve. Decline. Edit. The last thirty are reversible.
You flagged this for send earlier. The draft cites your March memo and last week’s call notes. One outbound message. No CC.
The approvals queue is mixed by design — sends, invites, and decisions live next to each other so you see the cost of the morning at a glance. Each card carries the same anatomy: intent, source, side effects, and the buttons that close it.
Cites your March memo and last week’s call notes. One outbound. No CC.
Conflicts with Mikhail intro. Two reschedule drafts prepared. Tomas + Aiyana, 45 min.
Source: meeting · acme · q3 review (14:22). Will update the Acme · Q3 review project page.
· pricing memo · approved & sent
· vendor reschedule · draft a picked
· follow-up to aiyana · reverted
· memory diff · auto-applied (silent)
The audit log is the run history of your assistant — each line written like a chief of staff’s notebook entry, not a system log. You can rewind any of the last thirty actions, or open a single line to see the source, the reasoning, and the effect.
The approval pattern is identical across surfaces — a send card on the board, a meeting follow-up in the chat, a memory diff in the vault. You learn the gesture once and carry it through the whole product.
Will update Acme · Q3 review and the agenda page. Source linked.
If you want autonomy that grows one rung at a time — never a switch flipped on without your eyes — apply to onboard.