Communication Capture

Communication capture is not implemented yet. It is the target product layer that should connect the places where B2B work appears, preserve source context, and turn source activity into relationship events.

Target sources#

• Email threads and shared inboxes
• Slack Connect channels and Microsoft Teams shared channels
• Customer and vendor portals
• Web forms
• Shared docs
• Call notes and meeting transcripts
• CRM, ERP, finance, procurement, support, and project activity
• Contract redlines and signed PDFs

Target event shape#

Every captured item should eventually become a source event with:

• source medium and source URL
• original timestamp and ingestion timestamp
• sender, recipients, organizations, and inferred participants
• relationship and workstream resolution
• attachments and linked records
• extracted decisions, asks, risks, deadlines, terms, and obligations
• confidence, sync status, permission state, and approval state

Target principles#

• Source-preserving: keep the original channel, author, timestamp, and artifact.
• Relationship-first: resolve events to relationships before internal workflows.
• Multi-party: support more than one organization, workstream, or permission boundary.
• Approval-aware: require review before sensitive external publication or downstream writes.
• Connector-general: avoid encoding one provider's model as the whole domain model.

Current status#

There is no connector framework, event store, thread stitching, attachment extraction, deduplication, or outbound provider delivery in the current repository.