Archie knows where you are standing
The dock is page-aware. Open it on a company record and Archie sees that record. Open it on a pipeline, the inbox, or a document, and the context follows. You do not paste things in or explain where you are. The question “what is the state of this one” means the record on your screen.A memory that compounds
Chat is not stateless. What Archie learns lands in the workspace brain: client nuances, your conventions, decisions, preferences, all shelved by Area so the right context surfaces for the right question. The brain cleans itself on a nightly cycle, re-filing and pruning so it compounds instead of rotting into a junk drawer. This is the mechanism behind your practice compounds: the longer you run it, the less re-explaining each conversation needs.From conversation to work
Chat is a front door, not a cul-de-sac. An intent you give Archie in chat routes to the specialist and Runner it maps to, and what comes back is real work product: a draft in Documents, a task on the board, a note captured and filed. The conversation produces artifacts that live in the workspace, not answers that die in a scroll buffer.The unread count on the Chat tab follows the same convention as Email: the tab reads “Chat (3) · Torchrunner” so you can see waiting messages from anywhere in the browser.