Pillar 04 · Team Comms

Aligned conversations. Sealed privacy.

Channels where Sarthy listens silently and aligns the work. Direct messages where Sarthy never listens at all. The difference is architectural, not a policy you can toggle off.

Project channels

Threaded conversations attached to projects, tasks, decisions. Sarthy Agent observes silently and checks for alignment. Never interrupts unless called.

DMs sealed by design

Direct messages between people are never alignment-processed. Enforced at five separate layers, not a toggle. Sarthy genuinely cannot read these.

Meeting notes

Typed capture during meetings. Action items parsed automatically with assignees and dates. Linked back to the originating decisions. Followed up.

Pr03 · DMs sealed by design

Five layers between your DMs and the alignment engine.

Layer 1 · DatabaseDM table has no alignment column at all
Layer 2 · APINo endpoint exposes DM content to the agent
Layer 3 · AgentCode path rejects target_kind = dm_message
Layer 4 · SearchDM content excluded from the index
Layer 5 · MCPMCP tools cannot return DM content

"Privacy by architecture, not by policy."

Notifications

One inbox. Smart digest.

Critical events in real time. Routine events as a fifteen-minute digest. Per-template preferences. Coalesced when the same thing happens many times. Mentions always land. Bulk actions for the inbox.

  • Bell icon with live count, dropdown for quick triage, persistent inbox at /inbox
  • WebSocket real-time delivery with DB-reconcile-on-reconnect
  • Tiered retention: unread 180 days, archived forever

See sealed DMs in action

Inspect the architecture yourself.

Twenty minutes. We walk through every layer of the Pr03 seal. You see the database schema, the API surface, the agent code, and the test suite. No marketing slides.

Book a demo