What the hub reads, what it cannot reach, and how to install.
About
One place to see everything, and no place to change it
Meow is a Discord bot with 12 systems and
90 commands. This hub is the map: what it does, what
governs each command, what the deployment is doing right now, and the
decisions behind where it runs. It exists because the alternative was
archaeology β reading six files to answer "is the market module on for
this server".
What this page is built from
real data
The same feature registry the bot validates at boot.
The same command-gate map it publishes to Discord.
The same counted windows /activity reads.
The same configuration audit the console shows.
Nothing here is a fixture or a screenshot. If a number on this hub is
wrong, the bot is wrong about the same number.
What it cannot reach
nothing that writes
No database. The hub has no connection string at all.
No session, so no server's settings and no member list.
No message sending, no scheduled post, no switch.
No credential that could be used to obtain any of those.
Its only network call is a GET that merges two endpoints which are
already public and already answer in counts rather than names.
What it is not
honest limits
Not a replacement for the console, which is where work happens.
Not a status page with an uptime guarantee behind it.
Not a mirror of any particular server's configuration.
Not for sale, and carrying nothing that is.
Where a question needs a signed-in answer, the page says so and links
there rather than guessing.
Trust
The pages worth reading before you install anything
These are the bot's own legal pages, written for the same deployment and
served from its public site. If something here disagrees with them, they
are the ones that govern.
Adding it to a server is a plain Discord invite with the permissions it
needs and nothing more β including the ones that are easy to omit and
then expensive to explain, like Manage Roles for the
default-role and level-role features. The console is where you configure
what it does once it is there.
Add it to a server
invite ready
The link asks for the permissions the features actually use, and for
Administrator alongside them, because a bot that was added without
it cannot post a moderation log, cannot assign a level role, and cannot
run the lockdown commands β failures that only show up later, in a
server, as "the command does nothing".
Signing in with Discord shows only the servers you actually administer,
and the console's own view of a server is scoped to it. If you run more
than one, the console's server switcher is where you choose which one
the switches, the composer and the scheduler act on.