The What
Responsibility is the missing layer.
Work is distributed across messages, tickets, documents and meetings. The responsibility that work creates belongs to none of those systems — so it lives in people's memory, and memory is where things get dropped.
The why
The object nobody owns.
Every system in your stack holds a piece of the record. Chat holds the conversation. The tracker holds what somebody remembered to write down. The repository holds the change. The calendar holds the date.
None of them holds the obligation — who owes what to whom, on what basis, what it is costing while it waits, and what would count as genuinely finished. That is not a gap any one of them can close, because it is the part that spans all of them.
The what
A system of record for what is on you.
Open Threads keeps that obligation visible, explainable and moving until it is closed for real. Not a task manager, which starts one step after the hard part. Not a search tool, which finds information rather than commitments. Not an assistant that summarises your day and forgets it.
One ledger of what is currently yours, with the evidence attached — and enough understanding of it that you can work through it by asking.
The who
Who is building it.
Open Threads is being built by a small group of independent product and technology professionals who believe important work should not disappear between systems.
There is no sales organisation. If you apply to the design-partner programme, the person who replies is one of the people building it.