Ingestion

Ingestion is how external events become actionable signals inside matic. Every human message, webhook payload, scheduled routine emission, and system event passes through this part of the work lifecycle before downstream interpretation and routing take over. Understanding the ingestion pipeline is essential for configuring channels, debugging signal routing, and extending matic with custom event sources.

Signal Sources

Signal Sources explains the external origins that produce signals: human messages on channels, routine emissions, webhook payloads, system events, agent-to-agent messages, and metric threshold crossings.

Channel Adapters

Channel Adapters covers the per-channel listener and sender implementations for Slack, Telegram, Discord, email, webhooks, and terminal workflows that convert channel-native events into canonical signals and deliver outbound messages back to each platform.

Signal Normalization

Signal Normalization describes how raw channel events are converted into the canonical SignalPayload envelope, structuring text, files, references, and transport metadata into a uniform shape that downstream interpretation can rely on.

Routing Hints

Routing Hints details the annotations attached during ingestion, including @agent mentions, @group handles, scope references, and subscription matches, that guide the router toward the correct recipient without requiring centralized triage.

Deduplication

Deduplication explains how matic detects and collapses duplicate signals arriving from the same event across multiple channels or retry paths by using normalized payload hashes within a configurable time window.

Dead Letter

Dead Letter explains what happens when a signal cannot be routed: undeliverable signals are written to .matic/dead-letter/, held for manual inspection or automatic recovery, and expired with an audit trail if left unresolved.