Telegram as an operator interface
Progress, trusted decisions and a clear boundary around control.
Useful messages, not noise
Report a changed state, a concrete blocker or a decision with consequences. Batch routine progress. A silent worker is not automatically a failed worker; distinguish idle, waiting, executing and unknown.
Bind the actor
Administrator binding, decision identity, expiry and first-answer retention belong in the contract. A public connect button must lead to onboarding, not expose the private operator bot or grant access to someone else’s projects.
Acceptance
Test an authorised answer, an unauthorised sender, a duplicated answer and an expired question. Keep the decision history separate from worker claims.