OneAI Bot App

Community bot bridge

Bring the existing WAOC OneAI Telegram Bot into TheOne as a governed runtime without changing the bot code.

RuntimeBot

Bridgeread-only

Codeunchanged

1Register runtime

TheOne treats the existing Bot as an external App/Worker without changing its code.

2Check bridge

TheOne performs a read-only health and contract check.

3Route later

Future Telegram-triggered work can be governed by TheOne policy and proof.

Bridge Contract

TheOne registers the existing bot as an external community agent runtime. The bot repository is not modified.

Botlocal repo

Modeexternal

Codeunchanged

oneai.bot.oneclaw_bridgeBot keeps its Telegram context and existing OneAI to OneClaw execution path. TheOne only governs status, policy, proof, and future routing.

1. Health check: TheOne can check the Bot HTTP service without touching Telegram.2. Runtime registration: Bot appears as an App, Connector, Worker, and installable package.3. Safe execution: Bot-triggered OneClaw work remains inside the Bot's existing bridge and approval context.4. Next bridge: add a small Bot-side HTTP command endpoint later, only if you choose to change the Bot code.

Bot Memory

Bridge checks and community runtime context saved from the OneAI Bot App.

No app memory yetRun this App once to create a reusable memory pack.