✈️

TELEGRAM GATEWAY

@reachZionBot — a second front door to Zion

Telegram is a native channel adapter, not a separate intelligence. It receives Bot API updates, routes commands into the existing Zion core, and uses the same subscriber registry and construct scripts as WhatsApp.

A Real Telegram Session

Hover or click Neo’s phone to open the bot conversation

NEO @reachZionBot subscribe coffee Subscribed to coffee. Today’s sample edition Full brief at 4 PM IST weather Mumbai Mumbai · live weather API data · no hallucination 🔍 hover / click to explore Telegram on phone BOT API getUpdates · sendMessage persistent update offset TELEGRAM ADAPTER normalize channel tg:<chat_id> ZION CORE same brain as WhatsApp tools · safety · routing SHARED SERVICES subscriber registry construct scripts channel_transport.py

Gateway Architecture

One Zion brain — two messaging channels

TELEGRAM @reachZionBot subscribe coffee weather Mumbai photo · voice · text CHANNEL ADAPTER zion_telegram.py Long-poll getUpdates Persistent update offset Command normalization Photo + voice routing HTML-safe replies tg:<chat_id> channel-qualified identity ZION shared intelligence core search · tools · safety · routing SUBSCRIPTIONS Shared SQLite registry AI news · coffee · stocks · movies DevOps · gratitude · vacation · word self-service subscribe / unsubscribe DELIVERY channel_transport.py Telegram Bot sendMessage WhatsApp Bridge /api/send one brief · correct channel Telegram does not duplicate the brain — it adapts the channel

SHARED BRAIN

Telegram calls the same Zion functions used by WhatsApp instead of maintaining a second AI implementation.

CHANNEL IDENTITY

Recipients are stored as tg:chat_id, preventing accidental cross-channel delivery.

MULTIMODAL

Text, photographs, and voice notes are normalized before entering Zion’s command routes.

PARITY

Construct aliases, subscriptions, immediate previews, and daily briefs work across both channels.

Tech Stack

GatewayPython 3 · zion_telegram.py
TransportTelegram Bot API · long polling + sendMessage
CoreShared zion.py intelligence and safety routes
IdentityChannel-qualified tg:<chat_id> subscriber records
Deliverychannel_transport.py chooses Telegram or WhatsApp
✕
✈️ @REACHZIONBOT
subscribe coffee
5:01 PM ✓
Subscribed to coffee.
Your sample edition is being generated. The full Coffee Lover brief arrives at 4 PM IST.
weather Mumbai
5:02 PM ✓
Mumbai weather
Live conditions returned from the weather API—not guessed by the model.
Behind the chat
Telegram adapter → shared Zion core → tool or construct → channel_transport → Bot API reply.
The same subscriber database supports WhatsApp and Telegram without mixing identities.