Coexo/Building Blocks/Input Sources
Section 2Live

Input Sources

How signals enter the system — WhatsApp, Gmail, Plaud, Telegram, web monitoring, calendar.

Vision

Signals flow into the system from multiple sources — monitored automatically, checked on schedule, or provided directly.

🎯 Direct Input Direct messages to the assistant — text, voice, files, links.

💬 Conversations Real-time or near-real-time exchanges. WhatsApp, Telegram, Instagram DMs, LinkedIn messages, Discord, Microsoft Teams.

🎙️ Transcripts Captured spoken word, processed after the fact. Plaud recordings, Google Meet, Zoom, Teams meetings. Turns spoken conversations into searchable, processable text.

📧 Email Asynchronous, standalone messages across multiple inboxes. Often serves as a trigger for deeper content on other platforms.

🔄 Internal Reports Scheduled self-assessments — system health, database hygiene, innovation scouting, case progression, security audits. Findings surface as actionable signals, just like any external input.

🌐 Web & News Proactive monitoring of the internet — industry developments, market changes, relevant events. Identifies opportunities and risks that may never surface through other channels.

📍 Location & Presence Physical location data streamed from your devices. Where you are right now, where you've been, movement patterns. Enables location-aware recommendations, travel time estimates, trip reconstruction, and context enrichment — "you were at Marina Bay when you had that call." Future: geofence triggers that automatically shift context when you leave the office, arrive home, or enter a meeting venue.

Implementation

Direct Input (Telegram text/voice/files)

Text, voice messages, and file uploads via Telegram as primary input method.

WhatsApp monitoring

Automated monitoring and intake of WhatsApp conversations.

Email triage (Gmail via gog CLI)

Email intake and triage from Gmail using the gog CLI tool.

Plaud transcript processing

Processing of Plaud device recordings into searchable transcripts.

Telegram as primary interface

Telegram serves as the main real-time communication channel.

Calendar sync (Google + M365)

Bidirectional calendar synchronization with Google Calendar and Microsoft 365.

Web & News monitoring

Manual web monitoring in place — no automated scanning yet.

Instagram DMs

Instagram direct message monitoring and intake.

LinkedIn messages

LinkedIn message monitoring and intake.

Discord

Discord channel monitoring and intake.

Microsoft Teams

Microsoft Teams message monitoring and intake.

Internal Reports

System health, case progression, database hygiene, and innovation scouting reports.

Location & Presence

Physical location awareness via self-hosted GPS tracking. Enables location-aware assistance, movement history, and future geofence-based context switching.

Notes & Future Ideas

One adapter skill per source. Each handles channel-specific intake and normalizes into a shared signal format.