# `rho telegram`

## Purpose

`rho telegram` is a middleware adapter, not a core protocol.

It should let Rho notify or query a human operator through Telegram.

## Responsibilities

- send approval requests
- receive approval responses
- map Telegram actions back into structured approval artifacts

## Preserve From The Old System

- Telegram as a human approval transport
- Telegram not being the core agent-to-agent transport

## Simplify

- keep bot logic thin
- keep all durable state in Rho manifests, not Telegram messages
- avoid letting Telegram own approval semantics


## Important Rule

Telegram should only carry operator interaction.
The source of truth should remain local structured files.

## Testing
In local testing environments it makes sense to use the same bot and approve as the same person for two different identities, so there should be a way to register the same bot and same username for a given rho identity which will then be used to message back and forth. However to prevent bugs messages should contain which identities they are meant to be representing but those should not be changeable just by sending plain text messages as a hack / workaround.

## Future
- support other messaging systems
- make the messaging integration and its actions agnostic and leverage app specific features where beneficial
