The conversation kit. Content on one thread. Conversation on the other.
Start with the definition, because this entire package is built on it: content is anything that creates conversation. A score nobody sees changes nothing, and content nobody answers is not finished, it is unanswered. loosethreads turns the other three packages into living exchanges: displays that open conversations, threads that carry them, and interactions that knot every reader into the loop.
The names come from the loom, and the metaphor turns out to be the architecture. On a loom, the warp is strung first: the long, fixed threads. The weft is what the shuttle carries back and forth through them, pass after pass, and the passes are what make cloth. So it is here.
A competent front-end build for a client-facing scoring tool is four to eight engineer-weeks: design system decisions, API plumbing, state management, the login page nobody budgeted for. loosethreads collapses that to days, because the components arrive already speaking Radiance and Windfall fluently. The strategic effect is bigger than the savings: when an interface costs a day instead of a quarter, you build interfaces for ideas that would never have justified a quarter. Your product surface grows to match your imagination instead of your sprint capacity.
Start with WarpDisplays, the content everything else is woven through. Back to the Web SDK overview.