Now: protect the origin server
AlexAI is live in Team eR33t. The current priority is making the system easier to understand,
operate, inspect, and correct without sanding off the personality that made it useful.
Public clarity
A clearer home, crew story, command reference, architecture map, public docs, and
honest onboarding language.
Operator sightlines
Better visibility into status, memory health, activity, relationships, episodes, and
system behavior for admins.
Better memory, fewer ghosts
Improving storage, retrieval, importance scoring, correction paths, and cleanup for
long-term context.
Consent in plain English
Making memory, voice, data, and moderation expectations readable before a pilot is
requested—not buried after Alex joins.
Next: prove the model with selected pilots
Separate server builds
Separate server rules, memory scope, dashboard access, usage limits,
and public output controls for each pilot.
Owner controls
Practical controls for channels, voice rooms, generated media, public
logs, deletion requests, admin roles, and budget boundaries.
Pilot agreements
Clear written expectations for setup, support, costs, safety duties,
data handling, and what happens at the end of a pilot.
Launch checklist
Reusable onboarding notices that server owners can share with their
communities before AlexAI is active.
Later: make good setup repeatable
If selected pilots prove useful and controllable, the setup can become more repeatable. The
direction includes:
- Assisted onboarding paths for approved adult communities.
- Clear scoping and usage visibility for models, media, voice, storage, hosting, and
support.
- Server-specific personality configuration without cross-server memory or lore bleed.
- Better admin tools for memory export, deletion, auditing, and retention windows.
- Clear public pages for generated media, release notes, and server-specific
notices.
Things we refuse to fake
These are not current commitments. A convincing heading does not make unfinished work real.
Instant public install
Not available until tenancy, privacy, permissions, and support flows are reliable,
documented, and repeatable.
Enterprise promises
Formal SLAs, procurement paperwork, and dedicated support channels require a separate
commercial posture.
Child-directed communities
AlexAI is not designed for children and should not be deployed into child-directed
communities.
Automated judgment
AlexAI can support server culture and moderation workflows. It does not replace human
moderators or server-owner responsibility.
Bring constraints, not applause
Tell us what would make AlexAI safer, clearer, or genuinely useful in your server. Specific
constraints are better training data than enthusiastic adjectives. Tragic, but true.