Connectors let SIM-ONE Alpha receive messages outside the local terminal interface. Every connector normalizes external input into a trusted internal event and sends it through the same governed orchestrator.
The packaged release contract starts connector pairing from the first authenticated terminal session after Onboarding. That conversational setup flow is a pre-release gate. The current source checkout includes Telegram and the generic Web API; it does not include Discord.
The connector setup flow:
Connectors normalize and deliver messages. They do not bypass the orchestrator, protocol system, approvals, or worker boundaries.
Telegram requires:
| Setting | Purpose |
|---|---|
TELEGRAM_BOT_TOKEN |
Bot API credential |
TELEGRAM_WEBHOOK_SECRET_TOKEN |
Verifies webhook delivery |
TELEGRAM_ADMIN_USER_IDS |
Optional connector administrators |
TELEGRAM_APPROVED_USER_IDS |
Optional pre-approved users |
TELEGRAM_BOT_USERNAME |
Optional bot username for mention handling |
TELEGRAM_MENTION_PATTERNS |
Optional group mention patterns |
The stored direct-message policy defaults to pairing and is changed through
the authenticated Telegram admin API.
| Policy | Behavior |
|---|---|
pairing |
Unknown users receive a time-limited pairing flow |
allowlist |
Only stored or configured allowed users are admitted |
disabled |
All Telegram messages are rejected by the current connector |
Although the stored setting is named dmPolicy, the current source applies
disabled before distinguishing direct messages from groups.
The packaged release contract creates and delivers a time-limited pairing code when an unknown user messages the bot, then approves that request through the authenticated Telegram admin API. The current source includes pending-pairing storage and the pair/deny routes, but webhook ingress does not yet create and deliver the pending request. That final connection is tracked in Pre-Release Status.
For the current source checkout, add the expected user and chat through the
authenticated /api/connectors/telegram/allow route, then send a Telegram
message and verify the admitted request reaches the orchestrator. See
Telegram Operations.
Group access is configured per group. A group can require a bot mention and can restrict messages to an explicit user list.
Group configuration is stored in the connector database, not in prompt text. Removing a group or user takes effect at the connector admission layer.
External applications can use the Secure Web API. Non-loopback clients send
the configured API_SECRET in the x-api-secret header. The generic chat
ingress accepts web-api and tui; authenticated callers may select either
identity and must provide stable ownership fields. Callers cannot claim
Telegram or another trusted connector by changing a JSON field.
See the HTTP API Reference for routes and request requirements.
Scheduled jobs enter through durable orchestrator dispatch and retain the
runtime’s capability boundaries and run observation. Current schedule dispatch
does not persist or pass a trusted normalized-event id, so load_protocols and
scoped memory retrieval are unavailable during scheduled turns. Trusted event
handoff for scheduled protocol and memory access remains a release gate.
Schedule definitions and run history are stored in SQLite. Current run history
records terminal status and errors, not generated result content, and scheduled
results are not delivered through a connector. Result persistence and user
delivery remain release gates.