Architect layer

Telegram bot

The architect's own tool, built to make their work faster — and a live demonstration of how this project remembers.

About

What the bot is for in this project and how it is arranged.

Your starter bot is a working demonstration of how this project remembers. It is not a toy and not a placeholder. Everything it does is built from the same parts your own project has, so trying it out is the shortest way to see the memory of Fractera at work.

What it can do today

  • hear text and voice — a voice note is fetched and transcribed, and from then on it is indistinguishable from typing (an OpenAI key is required for that)

  • accept a photo, a video, a document or audio — the file goes into the media library and is READ, so a receipt sent without a word is still searchable

  • keep the whole conversation — both what it heard and what it answered — for as long as the server lives; that is what the Logs section shows

  • hand every message to this project the moment it lands — your own door at /api/telegram/hook, with a shared secret; while that wiring is in place the PROJECT answers, not the service

  • knock on the project on a schedule, so a reminder can fire while nobody is looking at the site

  • send back: your project can write text and files into the chat

What it does not do — said plainly

  • one linked chat, yours. Other people can write to the bot and their messages reach the project, but the linked chat stays the default recipient, and nothing here collects a list of other people

  • no mass mailing. One bot, one messenger, one conversation at a time — a loyalty service writing to thousands is a different product

  • two of its own phrases (the greeting and the reply after linking) are English and live inside the service. This project cannot translate them

  • without an OpenAI key a voice note arrives without text — the message is kept, but nobody transcribed it

  • nothing is deleted automatically, so the journal only grows — the disk of your server is the limit

Where the boundary is. The channels service belongs to the platform, not to your repository: on the server they are neighbours, and on your laptop the service is not running at all. That is why these screens say the service is unavailable there — nothing is broken, the bot simply lives on the server.

How to get a bot. Ask @BotFather in Telegram for a new bot, take the token it gives you, and paste it into Settings here. Then link your account and write to the bot — the first message appears in Logs.

Powered by Fractera