Running your day · Lesson 2 of 3
How does YAGNI triage your email?
Published June 9, 2026 · Updated August 14, 2026
YAGNI reads your inbox and splits it into two honest states: needs you, or handled. Handled items carry a Receipt stating exactly what happened, with the tool call underneath. Items mirror the source, so archiving a thread in Gmail clears it here too, and nothing you already handled ever resurfaces.
What are the two states?
Needs you, or handled. A needs-you item is a reply only you can write or a call only you can make. A handled item is work the agent already did, with the receipt to prove it. There is no third state and no manufactured urgency; the lane’s job is to be finite, so you clear what is yours and get back to work.
What does an honest Receipt mean?
Two promises. First, every handled item states exactly what happened, with the actual tool call folded underneath, so trust never has to be blind. Second, every item reflects the current state of its source: archive, trash, or mark a thread as spam in Gmail and it clears here too. The lane never claims something needs you after you already handled it where it lives, and a thread you replied to never comes back as a work item.
What happened to everything that is not shown?
Triaged. The routine was handled and logged, the noise was filed, and one low-signal message is not treated as meaningful unless it is part of a larger pattern. You can always open the triage view and audit the calls: what arrived, what was handled, what was filed, and why.
Can someone else run triage for you?
Yes, and it is one of the highest-leverage ways to use the lane. An assistant or ops lead can work the email lane for an executive: clearing the handled receipts, answering what is theirs to answer, and forwarding only the items that truly need the principal. What counts as high priority is taught the same way everything else is taught, by the calls whoever works the lane makes, and pulling a filed item back teaches the Team what should never be filed again.
Where does email live in the app?
In its own lane, labeled Email in the navigation, so volume never drowns out the Decisions in the Feed. Items that need you join your normal walk like any other decision, each with its draft and its chat. Email is the busiest source most workspaces connect, and the lane’s design goal is that it stays a list you finish.
Common questions
Why is there no urgent-red state?
Because urgency theatre is how tools manufacture attention. Email has two honest states: it needs you, or it is handled. If something is genuinely consequential it sits near the top of the needs-you list; it does not flash at you.
Does YAGNI send email on its own?
Replies are drafted and wait for approval. As a Team earns trust on the record, routine internal handling widens, but an external send is exactly the kind of irreversible act that stays gated at every level, forever.
Is my inbox visible to the whole workspace?
No. Personal sources attach only through Settings, with your explicit consent, and a workspace-wide account never auto-attaches a personal source. Who can read what a Team sees is governed by that Team's privacy setting.
Can it triage Slack too?
Connected Slack feeds your Teams the same way: what the team is saying and deciding becomes context for the work, and threads that need a person surface as items. Direct messages stay private, always.