System Overview

RNDRNTWRK’s architecture connects five kinds of work: operating agents, producing media, establishing identity and authority, creating interactive experiences, and moving and allocating value. The components are being developed and integrated at different stages. This overview explains their responsibilities and how they relate to one another.

​

Five Capability Jobs

​

1. Operate intelligence

Agent operations need models, tools, planning, memory, budgets, scheduling, execution, and recovery. Alice is the agent RNDRNTWRK uses to develop and test its systems for research, planning, coding, and media operations. An Agent Fixture organises capabilities around a defined objective, with the tools, permissions, resources, and expected outputs needed for that work.

​

2. Produce and operate media

Media work includes live and recorded programming, production, publishing, archives, sponsor segments, and interaction. 555stream is the media environment. Its documented workflows cover stream destinations, scenes and overlays, guests, recording, clips, and programming between streams.

​

3. Establish identity and authority

The system needs to connect an action to the person, agent, company, wallet, or service involved. It also needs to represent the actor’s role, delegated permissions, available resources, budget, and constraints. 555ID and the surrounding policy and permission work address those relationships. Authority includes what an actor can do and the conditions under which that authority changes or ends.

​

4. Create interactive participation

Games, challenges, simulations, and shared activities give people and agents ways to play, learn, test ideas, contribute, and compete. 555 Arcade is the interactive environment. VAP’s participation-record design concerns how sessions, actions, and outcomes can be recorded and attributed under an experience’s rules.

​

5. Move and allocate value

SW4P is the intelligent routing and settlement system for moving value across the internet. It coordinates route selection, fees, execution, confirmation, recovery, and accounting for the result. SW4P Earn extends SW4P’s economic model into source-aware allocation, claims, rewards, payout schedules, reserves, and reconciliation. Current status: SW4P Earn is not yet publicly available. No staking, liquidity, reward, or claim programme is currently open.

​

Products, Shared Rules, and Operator Tools

These responsibilities appear in different parts of the ecosystem:

• Products present an experience: media through 555stream, interactive activity through Arcade, and settlement workflows through SW4P.
• Shared rules and interfaces connect identity, authority, ownership, participation, and value. VAP describes participation records, AGG describes payment-routing coordination, and Hyperlink describes programmable payment requests.
• Operator tools organise the work: CTRL Panel concerns stream controls, while Alice and agent workflows concern defined tasks, tools, memory, and recovery.

A capability can support several products. The same product can draw on several capabilities.

​

How an Activity Connects the Parts

An activity starts with a purpose and terms: who is involved, what resources are available, who can act, what should be produced, and how ownership or payment will be handled. The relevant products support the work. Records connect the actions and outputs to participants, permissions, resources used, and amounts owed. Where payment is involved, settlement records show what happened to the transfer. The activity’s funding and agreements determine its costs, recipients, and allocations. A participation record is evidence of an activity; the programme’s rules determine what that activity means for access, ranking, or any economic allocation.

​

Illustrative Flow: A Creator Stream

1. Define the stream, collaborators, permissions, and any commercial agreements.
2. Prepare destinations, layouts, overlays, guests, and the media to be used.
3. Choose interactive activities that fit the programme and the available product features.
4. Record relevant participation and results under the experience’s rules.
5. Handle any payments according to their funding source and agreements, with SW4P in the settlement role.
6. Retain the programme’s work and records, and plan any follow-up publishing or activity.

CTRL Panel and agent workflows have distinct roles within that process. The supported controls and automation are described in their product documentation.

​

Illustrative Flow: Alice in Arcade

A game can provide a bounded environment for developing and testing agent interaction.

1. The game defines the state, observations, and actions available to an agent.
2. Alice receives the permitted context and selects actions within those limits.
3. Game and service logic process the action and update the session.
4. The interface presents the resulting game state.
5. Records of the interaction support review of the session and the agent’s behaviour.

Specific control mappings and game mechanics are described in Game Mechanics & Possession.

​

Implementation Responsibilities

The capability jobs describe what the system is for. Implementation responsibilities describe how its parts support that work:

• Clients: browser products, overlays, and controls.
• Edge and media delivery: encoding, storage, caching, and distribution.
• Services: authentication, state, APIs, participation records, and events.
• Agent runtimes: model and tool use, memory, permissions, and recovery.
• Onchain components: asset records, authorisation, and settlement, with programme-specific economic arrangements where applicable.

The System Map follows these responsibilities and their interactions.

​

Go Deeper