Channel gateway — the normalized boundary between external surfaces and the runtime, per `docs/tools/CHANNEL_GATEWAY_MESSAGE_ADAPTERS.md`. Every channel (Telegram today; Slack / webhook / iMessage later) implements one `ChannelAdapter` contract and produces one normalized `JiggaE
# Source: https://github.com/JIGGAI/JIGGA | License: MIT | Copyright 2026 JIGG AI
# Provided via justclaw.it.com; keep this notice with the code.
"""Channel gateway — the normalized boundary between external surfaces and the
runtime, per `docs/tools/CHANNEL_GATEWAY_MESSAGE_ADAPTERS.md`.
Every channel (Telegram today; Slack / webhook / iMessage later) implements one
`ChannelAdapter` contract and produces one normalized `JiggaEvent` shape. The
listener/supervisor then route every channel through the same path:
adapter.poll → JiggaEvent[] → identity/policy check → task → agent
Adding a channel = implement `ChannelAdapter`, register it in `ADAPTERS`. No
listener changes. This is the layer the ad-hoc Telegram path skipped (B1).
"""
from __future__ import annotations
from dataclasses im
... (truncated -- full source via MCP)
See the full source, get the GitHub permalink, and search 40K more like it.
Get a free API key