One page for each thing she can do
Every plugin has its own page, and every page says what the thing stores, what it reaches, and how it fails.
Consent-gated archive
She sits in a chat group and keeps a record of what is said there, but a member's messages appear on the public web archive only if that member personally asks her to publish them, and they all come back down the moment the member changes their mind.
Archive capture ships on
Music bot
The operator uploads his own music, audiobooks and adverts, sorts them into playlists per bot, and members ask in plain language for a track, which arrives in the chat as a real playable message, on request or on a gentle timer with hard daily limits.
Music Library, and Member Uploads (play back) ships off
Channel bridge
The bot follows a broadcast channel and repeats each new channel post into a chat group as a scheduled announcement, word for word, labelled with where it came from, and the operator can additionally put those announcements on the public website, per channel, named or unnamed.
Channel bridge ships off
Knowledge base
The operator gives the bot text documents through the console, and she answers members' ordinary questions from them, printing which document an answer actually used, and admitting plainly when they do not cover the question.
Knowledge base ships off
Web search
When a member explicitly asks her to look something up, she sends just that question to a search engine, answers from the result snippets, and prints links to the pages she actually used, and when the results are missing, irrelevant or unjudgeable she says so instead of guessing.
Web search enabled ships off
Welcome bot
When somebody new joins a chat group, the bot greets them once, with words the operator wrote himself, sent publicly in the group, into the member's private support thread, or as a direct message.
Welcome enabled ships off
Crypto ticker demo
Ask her in the chat what a coin is worth, "price of 1 monero", "0.5 eth in usd", and she answers with a live market price, with every ticker permanently pinned to one specific coin so the same question can never quietly start meaning a different token.
Crypto prices enabled ships on
The same six questions, on every one
A feature list tells you what a product does when it works. These pages are written to answer the other question.
What each page answers
Every plugin page answers the same six questions, in the same order: what it does, what a member sees, what the operator turns, what it stores, what it reaches outside this machine, and how it fails. The last one is the one most product pages leave out, which is why it is on all of them here.
Each also carries one real interaction, taken from a running system rather than written for the page. That is the part of a product that cannot be copied from a feature list, and it is the part that shows whether the thing works.
Why the number here is never wrong
There are 7 plugin pages because there are 7 plugins. This page reads the site's own page tree, so a plugin that is added appears here in the same change that adds its page, and one that is removed leaves no card behind.
Per bot, and mostly off
Nothing here is on because it was built. Each is a switch on a single bot, and most of them start closed.
One bot at a time
Every one of these is a switch, and the switch is per bot rather than per installation. One bot in a support group can keep the archive and answer from documents while another, on the same server, does neither.
2 of the 7 ship on: Archive capture, Crypto prices enabled. The rest are off until somebody turns them on, which is the right default for anything that reaches outside the machine or speaks without being asked.
The one that keeps a record
Archive capture ships on because a bot that keeps no record of a support conversation is not much use, and capture is not publication: nothing a member says reaches the public web until that member asks for it. How consent works