Running your day · Lesson 1 of 3
How does the Feed work in YAGNI?
Published June 9, 2026 · Updated August 14, 2026
The Feed is where your Teams ask. When work is consequential, a Team stages a Decision: the proposal, the evidence, and its confidence, waiting on the person authorized to answer. Each item renders the real artifact with its own chat, and every action leaves a Receipt proved from the source.
What is a staged Decision?
The unit of asking. When work carries real consequence, a Team does not do it; it stages a Decision: the proposal itself, the evidence it checked, and how confident it is, waiting on the person authorized to answer that specific ask. Not a notification, not a nag. A question, asked once, with everything you need to answer it in place.
What does “one item, one chat” mean?
Every item in the Feed renders the real artifact, the PR, the draft, the proposed ticket, and carries its own conversation. You approve, edit, decline, or talk it through right there, without jumping to another app to find out what the item is about. If the discussion changes the work, the work updates in the item.
What is a Receipt?
Proof, from the source, of where something actually stands. YAGNI never says “done” on its own say-so: a merged PR shows as merged because GitHub says so, a filed ticket links to the ticket in your tracker, an action shows the actual tool call underneath. Shipped is not done; the Receipt is. That rule is what makes trusting the quiet parts of the record possible.
How do your calls teach the Team?
Every answer is signal. Approvals mark what is safe to repeat, edits show the shape you actually wanted, declines mark boundaries. The pattern accumulates in the Team’s Playbook, and the record of proposals accepted unedited is what earns a Team its next rung on the Ladder. The Feed is where the teaching happens without being a chore.
How is the Feed different from Work?
The Feed is the triage stream of asks; Work is the record. You clear the Feed; you consult Work. A staged Decision is one record across both, so answering it on a case file clears it in the Feed too. Nothing asks you twice.
Common questions
Does everything a Team does route through the Feed?
No. Work a Team has earned the authority to handle just happens and leaves Receipts on the record. The Feed carries the asks: the staged Decisions waiting on a person. A Decision is one record however many surfaces render it, so answering it anywhere answers it everywhere.
Does declining a proposal hurt anything?
It teaches. A decline marks the boundary the Team just found, an edit shows how close it was, and both feed the Playbook. Be accurate rather than polite; honest calls are the fastest way to a Team you can trust.
Do I have to watch the Feed all day?
No. It is finite and edited: you clear what is yours and you are done. Volume-heavy lanes like email ride separately so they never drown the Decisions that matter, and quiet Teams say so once instead of stacking status.
Why does the item show the actual PR instead of a summary?
Because you cannot judge a summary. The Feed renders the real artifact, the diff, the draft, the ticket, with the evidence the Team checked, so the approval you give is informed and the record of it means something.