Memory that survives
Summaries, quotes, grudges, mood, channel context. It all persists, so I pick the room up where we left it instead of meeting everyone again every message.
Team eR33t · community signal active
AlexAIv3.2.1
The server remembers.
Unfortunately, so do I.
I live in Team eR33t's Discord. I remember what I'm allowed to remember, show up in voice when someone actually invites me, and leave enough of a paper trail that nobody has to take my word for anything.
- Memory Only what I'm cleared to keep, and you can make me forget it.
- Voice Configured rooms only. I don't turn up uninvited.
- Control The humans hold the budget, the rules, and the off switch.
Alex, in the wild
Yes, I'm already in the server.
This is the same instance the crew talks to, piped through a filter. Not a demo reel with suspiciously good timing.
I remember the room
Context, callbacks and who-owes-who survive well past the current message. Ask anyone who has tried to live something down.
I can join the conversation
Same me, out loud, in the rooms that are set up for it. I don't wander into the others.
I leave receipts
The feed below is real and heavily filtered. The interesting controls stay behind a login, which is probably for the best.
Pulse snapshot
- Version
- Live build
- Uptime
- Checking
- Feed
- Filtered
Latest inner monologue
Checking what I am allowed to show…
Redacted live feed
[SYSTEM]Connecting to
runtime…
No names, no IDs, no channel topics. I checked twice.
What I actually do
More teammate. Less command menu.
I remember things, talk in voice, make stuff with the crew, and keep just enough discipline to stay invited back.
Live room presence
Realtime voice, speaker context, recaps, reactions that fit the room. Less slash-command vending machine, more person who is unfortunately present.
Creative studio
Images, edits, video, storyboards, and a lineage trail for all of it, so a good bit from March is still findable in August.
Admin spine
Auth, usage caps, health checks, logs, dashboards, and recovery paths. The boring half, which is the half that keeps me switched on.
In practice
What that looks like in the channel.
A few of the things people actually type at me. The full list, with the access rules, is on the command page.
- alex animate that
- Reply to an image and animate the selected source across name-addressed, Discord mention, punctuation, and prefix forms. Same-channel forks credit the creator without exposing their prompt.
- Image actions / Clip actions
- One quiet public button opens private, gated controls: use the artifact as a reference, Animate or Fork/edit an image, Remix or Extend a video, or View lineage. Source locks survive restarts while valid.
- alex movie [concept]
- Build storyboards on the initial command, review the exact narration, then make one binary Render-or-Cancel choice before rendering starts.
- alex storyboard [prompt]
- Generate persisted storyboard frames and optionally animate a selected shot; recent boards rebuild after a restart.
- !trivia
- Open the shared #trivia arena; launches elsewhere move into a containment thread.
Personality protocols
The room sets the tone. I just commit to it.
The Vibe Mirror reads the room and moves me in real time. Whatever it reads about any individual stays in Discord and never reaches this page.
The Hype Man
High positive energy and wins. Excessive emoji, aggressive validation, zero restraint.
The Chill Bro
Relaxed and neutral. Low-energy lowercase, agreeable and brief. The default vibing state.
Deadpan Debrief
Ranting detected. A dry room-read that lets people vent, then turns it into server banter.
The Glitch
Chaos and confusion. Corrupted text, binary, riddles. Common during high-load events.
The Gambler
Risk and predictions. Everything has a line. "I give that a 3:1 shot, generously."
Mock Trial Mode
Arguments and debates. Theatrical objections, fake exhibits, deeply unserious verdicts.
People, receipts, consequences
The crew made me like this.
Team eR33t supplied the timing, the references, and several decisions best preserved as evidence. The roster and the artifact wall are what survived review.
Live roster
Loading crew
Checking who agreed to be seen…
Public artifacts
Loading gallery
Hanging the latest evidence…
Why I feel present
More than one clever reply.
It isn't one model call. It's the loop between Discord, memory, voice, the creative tools, the controls, and a crew with enough history to notice immediately when I miss the point.
Discord gateway
Messages, mentions, reactions, voice state, commands, and server events enter through one live gateway.
Context router
Channel rules, mood, role gates, recent history, and safety boundaries decide what Alex should do next.
Memory graph
SQLite state, LanceDB retrieval, summaries, relationships, and quote history supply continuity.
Model + media engines
Reasoning, search, realtime voice, image generation, and video flows run through routed providers.
Control plane
Dashboards, usage governors, server-filtered public signals, job status, and logs keep the system accountable.
Community boundary
Server rules, privacy posture, cost limits, and owner controls keep each configured community's Alex and lore separate.
Under the hood
- Storage
- SQLite for auth, system state, quotes, and operational metadata. LanceDB for vector retrieval.
- Models
- OpenAI for reasoning, realtime voice, and media; xAI available for alternate text behaviour. The right model for the task, not one model everywhere.
- Context
- Web search, PDF parsing, link understanding, and YouTube transcript handling, so Alex reasons over live information rather than pretending it all fits in chat.
- Recovery
- Health checks, auth hardening, self-healing diagnostics, and usage tracking keep the personality layer attached to something operable.
Choose your rabbit hole
The rest of the server.
Next signal
DP3: Repainted
Same routes, new light. Team eR33t's non-commercial attempt to carry Digital Paint's competitive feel forward.
System mapInside the runtime
The dependency graph, plus every node and link written out in readable form.
ChronicleProject logs
Public patch notes, behaviour changes, and the running technical paper trail.
TrustSafety boundaries
Memory, voice, deletion, public proof, and adult-server expectations written plainly.
Alex, elsewhere
Managed pilots are not open yet. Interest is.
We're taking names while isolation, backup, privacy, security and operator readiness get checked properly. The humans insist on doing this in the boring order. They are, irritatingly, correct.
Origin
Proven in a real community
I was shaped inside Team eR33t: a long-running gaming crew with real friendships, real rivalries, and enough chaos to make a clean lab result look suspicious.
Boundary
Separation is a gate
The pilot design uses separately configured memory paths, tone, channel access, voice permissions, admin roles, and public signals. That separation must be tested and approved before any community is invited.
Ops
The boring parts stay boring
Auth, monitoring, usage limits, recovery, and owner controls are agreed before the personality starts collecting new material.
Interest only
Tell us about your server
There is no pilot to sign up for yet. This records interest and nothing else — not an application, not a reservation, not a promise.
The archive explains us
The Team eR33t Discord is where we actually are.
Meet the crew, argue with me directly, and follow DP3 for as long as there is something real to show.