What you are trying to do
You opened the Inbox. You read an item. Now you have to do something with it. Most tools at this point either leave you with a blunt "mark as read" button or, worse, leave the item sitting until you forget about it. Ship gives you three options on purpose, and records which one you chose.
The three dispositions are address, dismiss, and escalate. They are not synonyms. The difference between them matters in week three when somebody asks why a thing happened.
Address — you handled it
You hit Mark addressed when the item is resolved. You opened the stuck pull request and merged it. You opened the learning capture, agreed it was a real pattern, and filed a ticket to fix it. You read the daily retro, the numbers were fine, and the rest of your day continues.
Addressed does not mean "I read it." It means "I took the action that was needed, and this Inbox item should not come back." The system records who addressed it, when, and against which item. That record is the disposition log, and it is what survives turnover and re-orgs.
Dismiss — this does not need a response
You hit Dismiss when the item is real but does not require action from you. The most common case is a learning capture about a pattern you do not care to fix right now: yes, the agent noticed something, no, you are not chasing it this quarter. Another common case is a daily retro on a quiet day — you read it, nothing was on fire, you move on.
Dismissed is honest. It is not "I lost interest" — it is "I read this and consciously decided not to act." Ship records dismiss as a real decision, with a timestamp and an actor, the same way it records an address. A dismissed item does not come back tomorrow.
Escalate — this is bigger than the Inbox
A handful of Inbox items will be things that need more than a one-button disposition. A learning capture that, on a second read, points at a process flaw worth a whole conversation. A stuck-work item that has been stuck three times this week because of a deeper bug.
Escalate is your way of taking that item out of the Inbox and into the place where bigger conversations happen — a real ticket, a meeting, a doc. The Inbox is honest enough to say "this is no longer the right home for this." Ship records the escalation and the destination, so the original Inbox letter still points at where the conversation continued.
Why every disposition is logged
The cost of a decision you cannot retrace is higher than most teams realise. The customer asks why you killed a feature in March; the new VP of engineering asks why a particular control was loosened; the auditor asks who approved a change to a sensitive area. If those answers live in chat, they are gone. If they live in the disposition log, they are one search away.
We log disposition because operations work that is not legible decays into folklore — "I think the previous PM decided that?" — and folklore is what makes the next reorganisation painful. Treat the log like a finance ledger: small entries, made constantly, that add up to a real record of what the business actually did.
What this changes about your week
You stop accumulating Inbox debt. Every item gets addressed, dismissed or escalated — there is no fourth state called "I will look at it later." This sounds harsh until you live with it for a week and discover the Inbox is genuinely empty most evenings, because the buttons made the call easy.
You also stop arguing about old decisions. Six months from now, when somebody asks why a ticket was dismissed in May, you do not have to remember; you open the log and the answer is there, attached to your name, on the date it happened. That is the version of trust you actually want — not "trust me," but "look at the record."