Skip to main content
The roadmap follows the direction set out in the RNDRNTWRK Public Corpus: complete the first commercial loop, make partner programmes repeatable, turn reusable capabilities into a partner platform, and develop an open protocol. The releases below describe that progression. Individual modules advance according to the work they support, what partners need, and what can be reused. Product pages explain the scope and status of particular capabilities.

Release 1: The First Commercial Loop

Bring a useful objective through the full operating loop: work, output, economic activity, settlement, and a record of the result. Agent Fixtures organise the capabilities needed for the objective. These can include research, coding, product operations, media, streaming, outreach, integrations, and campaigns. SW4P provides the settlement role, connecting the payment instruction with routes, fees, execution, confirmation, recovery, and accounting. The aim is one coherent programme whose work and financial result can both be followed.

Release 2: Repeatable Partner Programmes

Turn the first loop into a repeatable way of working with partners. This direction brings together agent roles, identity and delegated authority, persistent context, reusable Fixture patterns, recurring media formats, sponsor material, and settlement instructions. Partner programmes help identify which capabilities are repeatedly useful and which costs or operating problems need attention. That experience shapes the modules developed for broader use.

Release 3: A Partner Operating Platform

Make reusable capabilities available as services and integrations that partners can adopt for their own work. The planned platform includes partner-specific agents and Fixtures, identity and operating policies, media and settlement integrations, company and token modules, and managed operations and support. APIs, SDKs, and deployment templates are part of this planned interface direction. A partner could use a particular capability—such as a media operation or settlement workflow—or combine several into an operating programme.

Release 4: An Open RNDRNTWRK Protocol

The long-term direction is for independent builders and operators to implement compatible services. Public interface specifications, compatibility tests, reference implementations, and a compatibility registry would make it possible to check whether different implementations work together. This could support multiple agent runtimes, media systems, identity providers, economic modules, settlement adapters, and applications within the same broader system.

Release 5: A Network That Can Keep Expanding

The corpus calls this long-term direction “abundance”: many participants adding capabilities, services, resources, and distribution to the network. Builders could create compatible products. Companies could run their own human-and-agent operations. Partners could supply infrastructure, liquidity, media distribution, and capital. The aim is for useful new relationships and capabilities to keep emerging from the wider network, with RNDRNTWRK continuing to develop products, services, integrations, and shared foundations.

What Shapes the Next Module

A capability advances when it helps recurring work, answers a partner need, reduces a meaningful cost, improves settlement capacity, or makes an integration reusable. Security, recovery, and interoperability also shape that choice. The release direction stays consistent while the order of individual modules responds to those needs. The VAP v2 Research, Audience Inventory, and Render Expand pages describe particular research and product concepts. Their details belong to those pages rather than a separate set of fixed phases here.

Follow the Product Work

  • Alice and the Intelligence Engine — Agent capabilities and operating assignments.
  • 555stream and 555 Arcade — Media and interactive experiences.
  • SW4P — The settlement engine and operation lifecycle.
  • SW4P Earn — Allocation, claims, rewards, payout schedules, reserves, and reconciliation.
  • Economic Model — Funding, costs, payments, and reinvestment.
  • For Developers — Architecture and integration responsibilities.
Current status: SW4P Earn is not yet publicly available. No staking, liquidity, reward, or claim programme is currently open.