Stop digging through a separate chat app to find what was decided on a line item or a pay application. Each thread anchors to the exact work object on the shared graph, and can settle into a decision of record -- the approver and the participants named.
Why it matters
Projected Messaging is the conversation layer of your operating surface. Teams threads, inline row discussions, and network direct messages all attach to the same records you are already working -- the project, the line item, the payment application, the change order. The agent keeps the right thread on the right object and pulls in the people who own that work.
Each chat thread binds to an object_type and object_id in acs_thread_anchors -- a Teams or ACS conversation pinned to the exact record on the shared cascade graph. The row-thread block projects that thread inline as cascade data, not a bespoke chat screen. Network DMs add governed 1:1 messaging with block, follower, and tenant gates.
The work, split
The agent anchors each thread to the right record and surfaces it inline on the row, so the discussion sits with the work. It routes the people who own that record into the thread, and enforces the block, follower, and tenant gates on every direct message -- the calm 80 percent of message traffic that never needs your attention.
You make the call that counts -- mark the thread resolved as an approval or an agreement. That click writes a typed row to the decision ledger, tied to the exact work object, naming you as approver and everyone who took part. The receipt is immutable and reads back on a record no one at the table can dispute.
How it works
Open the messaging surface for your seat or your community, and watch a thread settle into a decision of record on the exact line of work.