Launch Readiness Matrix

Last updated: 2026-06-28

Roadmap items move from idea to live public service through explicit status stages, so each capability can be read as historical, planned, implemented, deployed, or launch-ready.

Readiness Levels

Historical

Appears in roadmap history, alpha, devnet, or community-testing history.

Planned

Part of the roadmap, but not yet presented as a live public service.

Implemented

Runtime, contracts, configuration, or product code includes the capability.

Deployed

A named endpoint, chain, contract, session, or product environment exists.

Launch-ready

User-facing URL, address, docs, support path, and operating owner are in place.

Current Readiness Snapshot

Router primitives

Completions, delegate, validate, and factcheck are core route families. Delegate fans work across replica pools; validate aggregates validator sessions; factcheck depends on deployment configuration.

MCP, A2A, and x402

These surfaces turn Router Node into agent-facing infrastructure. MCP exposes tool-like router access, A2A supports agent discovery, and x402 enables pay-per-call workflows where configured.

Portal and router pools

The hosted product path maps API keys, model aliases, usage tracking, billing, and managed router pools into Cortensor sessions.

Corgent and Bardiel

Corgent packages delegate, validate, factcheck, arbitration workflows, and evidence flows for agents. Bardiel is a productized ecosystem agent surface using related primitives.

Mainnet-Lite and Mainnet-Full

Mainnet-Lite is the Arbitrum L2 Alpha launch path. Mainnet-Full is the COR L3 Beta launch path for higher-volume COR-native agent execution.

ERC-8004 and PyClaw

ERC-8004 is the registry and discovery alignment area. PyClaw is the local-first agent runtime for client-side and agent-side Cortensor workflows.

Launch Checklist

Network

Network name, chain ID, RPC, explorer, bridge, gas/token guidance, and current environment label.

Contracts

Contract addresses, explorer links, ABI source, deployment version, and module ownership.

Router

Public URLs, route families, auth policy, MCP/A2A status, x402 status, timeout policy, and session map.

Operators

Supported binary version, role list, runtime requirements, monitoring, upgrade policy, and runbook path.

Products

Portal/gateway URL, API key issuer, model aliases, billing/usage policy, customer support path, and managed pool behavior.

Security

Audit posture, incident response, restricted-address policy, payment support, privacy model, and known limitations.

Product Status Guide

Product area	Launch-readiness signal
Router Node	Public host, route map, session map, auth policy, model map, and operator runbook.
Portal/API gateway	Customer URL, key management, usage and billing policy, and support path.
Dashboard	Network selector, contract target labels, wallet permissions, node/session telemetry, and admin warnings.
Corgent	Product API, policy tiers, evidence schema, Virtual/ACP/ERC-8004 integration state, and support path.
Bardiel	Product URL, dashboard/app availability, staking/product boundaries, and active agent workflows.
PyClaw	Integration package, API examples, local runtime path, and supported Cortensor routes.