Responsibility Map
An overview of responsibilities within the architecture RNDRNTWRK is developing. Identity, permissions, budgets, and ownership connect these parts. Individual integrations determine the components and connections used.
Identity, permissions, budgets, and ownership connect these responsibilities. They determine which actor can use a resource or perform an action and how that action is recorded.
Components Within the Map
Clients and media
555stream concerns production, publishing, and interaction. CTRL Panel concerns stream controls, layouts, overlays, and scheduling. Arcade concerns games and interactive environments. The media design includes encoding, storage, caching, scene and session state, guest connections, recording, and clips. A selective forwarding unit (SFU) handles forwarding media between participants in a multi-party WebRTC arrangement; composition and transcoding are separate media-engine responsibilities. Capture components support recording and clip generation. Text-to-speech and avatar components concern the agent’s voice and visual presentation.Services and participation records
Application services handle requests, authentication, state changes, and event delivery. Databases and state stores serve different persistence and coordination needs within those workflows. VAP describes participation records and session-integrity checks. AGG describes payment-routing coordination; Hyperlink describes payment requests with the context needed to resolve and follow them.Agents and authority
Alice is the reference agent used to develop and test research, planning, coding, and media operations. Its runtime work covers tools, models, memory, knowledge retrieval, budgets, and recovery. 555ID and the surrounding permission and policy work connect actors to their roles and resources. An agent’s permitted observations and actions depend on the authority granted for its task.Settlement and economic programmes
SW4P coordinates the settlement lifecycle, including route selection, fees, authorisation, execution, confirmation, recovery, and accounting. An integration can involve asset exchange, execution-cost handling, or other route-specific services. Supported networks, assets, providers, and costs belong to the particular integration’s documentation. $555 is the coordination asset of RNDRNTWRK. Token holdings, points, and settlement assets have different roles. 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.Illustrative Data Flow: A Play Session
- A player or agent takes part in a game under its session and access rules.
- Game logic produces actions, score changes, or other relevant events.
- The session-record design associates those events with the participant and the permitted context.
- Service logic checks the record and updates session state.
- The interface receives the resulting state or ranking, and records are retained as needed.
- The experience’s rules explain any points or credits and how they are used.
Illustrative Data Flow: A Stream
- A creator prepares the stream’s sources, destinations, layouts, and guests.
- Media components handle the production and delivery work required by that configuration.
- Controls and session state coordinate scenes, overlays, and guest interactions.
- Permitted operator or agent tasks support defined parts of the workflow.
- Participation and programme records describe the activity and any commercial deliverables.
- Payment records connect the programme’s funding, costs, recipients, and settlement results.
Go Deeper
- System Overview — Understand the five capability jobs.
- API Reference — Read the documented interface families.
- 555stream — Explore the media workflow.
- Alice — Read about the reference agent.
- SW4P — Follow a settlement operation.
- SW4P Earn — Read the allocation model and current status.