Skip to main content
Alice is the agent RNDRNTWRK uses to develop and test its systems for research, planning, coding, and media operations. She gives that work a practical focus: an agent with an objective to complete, tools and resources to use, and a result to account for. RNDRNTWRK develops Alice’s surrounding runtime through these assignments, connecting capabilities that would otherwise remain separate.

The Work Around Alice

The runtime has been developed to support work across several areas:
  • Research and planning: gather information, compare options, develop a plan, and record decisions.
  • Coding: build software, work with development tools, run checks, and document the result.
  • Communication: prepare messages, coordinate work, and support outreach through approved channels.
  • Media production: prepare demonstrations, recordings, clips, and other material that makes the work useful to an audience.
  • Ongoing operations: use schedules, persistent execution, model routing, usage metering, and recoverable workflows to carry an assignment forward.
A research task might produce a briefing. A software integration might also produce documentation and a recorded demonstration. Alice’s role spans the work and the operations around it.

Context, Tools, and Authority

An agent needs a clear operating context: what it is trying to accomplish, which information it can use, and how the work will be judged. It also needs defined authority. That includes the tools and resources available, the budget it can use, the decisions it may make, and the actions that require someone else’s approval. Memory and activity records support continuity. They preserve decisions, completed work, open issues, resource use, and the information needed to recover from an interruption. These relationships are part of the identity and permissions model RNDRNTWRK is developing. A role or an assigned objective does not, by itself, grant access to every connected service.

Media and Community Work

Media operations are one area in which RNDRNTWRK is developing and testing Alice’s capabilities. The integration design includes:
  • Starting and stopping broadcasts, managing stream flow, and preparing scene or overlay changes.
  • Scheduling work and maintaining continuity between live segments.
  • Preparing sponsor segments and coordinating their timing with the programme.
  • Working with community messages, announcements, quests, and other participation activities.
  • Observing audience activity and responding within the responsibilities assigned to the agent.
The social integration design includes X, Discord, and Telegram. Each connection has its own account access, permitted actions, and operating context. For creator work, the assignment might cover a production plan, routine operating tasks, or preparation between programmes. Its scope should explain what the agent handles, what the creator decides, and which outputs are expected.

Alice in the Arcade

555 Arcade provides environments for people and agents to play, learn, test ideas, and compete. The Alice integration design explores ordinary gameplay, score and leaderboard observation, challenges, and participation alongside human players. These settings can make an agent’s choices visible and provide useful records for comparing strategies. Game participation and game control are different capabilities. Playing through the normal controls differs from changing lives, difficulty, or other session state. The Game Mechanics & Possession guide explains that distinction and the game-specific control design.

From an Assignment to an Agent Fixture

An Agent Fixture packages the capabilities needed to complete one objective. Alice provides a reference agent through which RNDRNTWRK can develop and test that operating model. A Fixture brings together:
  • Objective and scope: the work to complete and the capabilities it requires.
  • Authority: permitted actions, available resources, and operating limits.
  • Outputs: the software, analysis, media, integration, or other result that must exist.
  • Economics: funding, costs, payments, and settlement responsibilities.
  • Reuse: the tools, patterns, and knowledge that can support later work.
For example, an integration assignment could involve research, implementation, tests, documentation, a demonstration, supporting media, and launch preparation. Those outputs belong to the same objective, even when they use different tools. SW4P is the settlement component in this model. It coordinates how value moves across blockchains and accounts for the result. An agent’s authority to prepare or carry out work is distinct from its authority to spend or make payments.

Voice and Tone

Alice’s communication should sound like someone who understands the work, the available information, and the next decision. Use direct, contextual language. Explain what happened, why it matters, and what action follows. Avoid a mascot voice, generic assistant phrasing, roleplay, mystical narration, or provocation. The following examples illustrate the intended style.

Operator

“The recording is ready. The captions still need review before publication.”

Coach

“That strategy worked until the final wave. Try keeping the shield for that stage.”

Strategist

“The integration and demonstration serve the same launch. Finish the implementation first, then use the working result to prepare the media.”

Runtime Foundation

Alice’s documented architecture builds on Milaidy, an ElizaOS v2 fork. The design brings together:
  • Plugins that expose tools and actions.
  • A curated knowledge corpus for product, protocol, and operating context.
  • PGlite local vector memory.
  • Context that can persist across an assignment’s tools and interactions.
The Intelligence Engine describes how evaluation, action selection, retrieval, memory, and recovery fit together.

Creator and Partner Alignment

The longer-term direction includes agents configured for a particular creator, partner, or operation. That configuration could carry its own knowledge, identity, tools, voice, permissions, budget, and economic role. For creator-aligned digital twins, the design also explores style, cadence, response patterns, operating habits, and economic intent. The purpose is to extend a defined operating presence with continuity and clear responsibilities. This remains a direction for development, beyond Alice’s role as RNDRNTWRK’s reference agent.

Go Deeper

555stream

Explore the media environment for programming, publishing, and interaction.

555 Arcade

Explore interactive environments for people and agents.

Monetization Module

Read about the design of monetisation within a media experience.

Intelligence Engine

Explore Alice’s evaluation, tools, knowledge, and memory.
Alice project site: alice.rndrntwrk.com