One announcement, repeated into every group, word for word
Post once in a channel, and every room you name gets it, with the source labelled and nothing rewritten.
The question
post an announcement once and have it reach every group, and my website
Yes, and nothing rewrites it. She follows a broadcast channel and repeats each new post into the groups you map, as a scheduled announcement labelled with where it came from. An edit at the source updates her copy in place; a deletion removes it for everyone.
Who this is for
Anybody who announces things and currently repeats himself: a studio, a club, a shop, a project with more rooms than patience.
No model on the path, and a cadence that cannot die
Two properties matter more than the feature, and both are structural rather than configured.
There is no model anywhere on the forwarding path, so the only transformation is a trailing blank line trimmed, and there is nothing for a hostile channel post to instruct. The tick is a self-chaining job that books its successor before doing the work, so a failing tick cannot end the rhythm. When more than one post is pending it sends one digest rather than a burst.
What it will not do
It will not carry your announcements to a network without end-to-end encryption without saying what that costs. A bridge to such a network loses confidentiality at that hop, and no bridge to another network exists in the product today.
What this needs, and what state it is in
Read from the same table the ways-in page renders, so it cannot be current there and stale here.
The doors this touches
Over a chat network built
What runs today: the chat core embedded in-process, with no daemon and no exposed port, one directory as the only SDK importer, and one core hosting every enabled bot with commands serialized and events routed per profile
Over a web server, as an ordinary web assistantstarted
More than nothing, honestly: a demo route drives the real interaction engine, consent logic and persistence over the fake adapter, with a deterministic rules layer, a 25 message budget and synthetic data. The admin console and the public archive are web surfaces rather than chat ways in
The web door is the one most readers of this page assume they are buying, and it is not finished. The door that is built is a chat network you would have to adopt. That is the honest answer, and it will cost us some readers.
The pages that carry the checks
This page makes no claim of its own. Each one below is where the thing is written down with the way to verify it.
What to read
The channel bridge page carries the cadence, the digest, the per-channel web publishing and the confidentiality line beside the feature.