Integrate
Telegram bot boundary
@FpgaChatBot is operated from the separate fpgabot project and has its own data boundary.
Use when
- You need to distinguish the web/API runtime from the Telegram bot runtime.
- You are checking where bot history, payments and OpenRouter subkey metadata live.
- You want to use bot triage without assuming signoff or shared database behavior.
Outcome
- Bot data ownership is clear.
- Decoder API calls from the bot remain evidence-scoped triage.
- Operational notes point to the separate fpgabot deployment.
Data boundary
- The bot does not share the fpga.chat application database.
- Telegram request history, bot feedback and bot payments are stored by fpgabot.
- fpga.chat stores only its own product/API records.
Operational boundary
- Use the separate fpgabot project for deployment, migrations, webhook setup and bot smoke tests.
- Bot calls to the Error Decoder API are triage outputs, not signoff.
- Keep bot secret rotation compatible with migrated encrypted OpenRouter subkeys.