Running your day · Lesson 1 of 3
How does the Feed work?
Published June 9, 2026
The Feed is the doing surface: the short list of items that are actually yours. Each item is one thing with one chat, and it renders the real artifact, the editable email or document itself, not a narration of it. You approve, decline, or edit, and you clear the list to the bottom.
What is “one item, one chat”?
The Feed shows one item at a time, and every item carries its own conversation with @yagni. The draft reply to the stalled deal is one item; the chat pinned to it is where you ask “what did we quote them last time?” and get an answer grounded in the same rows the draft came from. Nothing about a decision lives in a second place.
This is the opposite of the app-switching loop the Feed replaces: read a notification in one tool, find the context in a second, write the answer in a third. Here the context, the conversation, and the artifact share a frame.
Why does the Feed render the real artifact?
Because a summary of an email is not an email. When @yagni drafts a reply, the Feed shows the actual editable message: the recipient, the subject, the body you can rewrite. When it proposes a change, you see the real thing it wants to ship. Approving means approving the artifact itself, never a description of it.
That is also what makes approval honest. You are not trusting a paraphrase; you are reading what will actually leave the building.
How do you clear the Feed?
Top to bottom, one call at a time:
- Approve when the draft is right. It ships back into the tool it came from, and the receipt lands teal in the Inbox.
- Edit, then approve when it is close. Your edit ships, and the Team learns from the difference.
- Decline when it is wrong. That is signal too, and the Team weighs it.
- Talk it through when you are unsure. Ask the item’s chat for the evidence, the history, or a different angle before you call it.
The list is short by design. @yagni already did the routine and filed the noise; the Feed holds only what is genuinely yours. Reaching the bottom is normal, daily, and the point.
What do your edits teach the agent?
Each edit is a captured signal of how you changed the proposal, and the pattern of your edits is what a Team’s Playbook is made of. Edit the same clause twice and the Team learns the rule, team-wide, so the third draft arrives already right. The Playbook lesson covers how rules are learned, owned, and reviewed.
This is why the first weeks of clearing the Feed feel like editing and the later weeks feel like approving. The work did not get easier; the agent got sharper. The result shows up in your edit rate, and when the agent is not pulling its weight, the guarantee is the honest backstop.
Common questions
Is the Feed like a notification stream?
No. A notification stream is infinite and tells you something happened somewhere else. The Feed is finite and holds the work itself: the real draft, ready to edit and ship. You clear it to the bottom, and the bottom exists.
What does one item, one chat mean?
Every item carries its own conversation with @yagni, scoped to exactly that item. Questions, context, and changes happen right next to the artifact, so nothing about the decision lives somewhere else.
What happens when I edit a draft before approving it?
The edit ships, and the Team learns from it. Captured edits are how a Team's Playbook forms: change the greeting twice and the Team learns your greeting. Your judgment compounds instead of repeating.
What kinds of items land in the Feed?
Drafted replies and follow-ups waiting for approval, proposed work-items, decisions a Team cannot make alone, and anything you asked @yagni to prepare. If it is in the Feed, it is yours.