Roadmap

Global roadmap.

Rollout phases for CAPPS access, Capsule verification, Layer 6 services, and expansion.

Core Terms

The roadmap uses the same definitions as the live docs.

Atomic AI Nexus

The public product surface.

CAPPS

The access-control and route-policy system.

Capsule

The verification session required before protected routes open.

Layer 6

The protected private core for sensitive services and vault logic.

AI Core

The private operational intelligence layer.

Phase Track

Expansion path

Phase 1

Stabilize verified portal lanes, Review CAPPS, AI Core operations, utility checkout, and proof-backed public state.

Phase 2

Scale CAPPS marketplace builds so services, credits, and access products all move through the same Capsule-governed fee rail.

Phase 3

Reframe Capsule plus gateway relay as an authenticated API transportation mesh for protected inter-system movement.

Phase 4

Apply Layer 6 control logic to super-secured vault surfaces for digital banks, protected treasuries, and asset-control environments.

Phase 5

Expand regionally and internationally through controlled deployments, policy packs, and infrastructure partnerships.

Operational Roles

Command, monitoring, and verification roles inside the stack.

Command System

The command system keeps the Layer 6 runbook coherent: it routes actions, picks the right lane, and stops public activity from crossing into protected control paths.

Cyber Defense Agents

Defense agents watch for abuse, drift, failed policy checks, and surface changes that should trigger a lock or a review before users reach core services.

Red-Team Agents

Red-team agents actively probe the stack for weak points so the build can be tightened before attackers or accidental misuse find them first.

Scouts

Scouts watch the edges of the system and report early signals, route changes, and rollout gaps so ops can move before a defect becomes visible.

Sentries

Sentries hold the boundary rules: no Capsule, no move; no proof, no claim; no write access without the founder-safe control path.

Internal POS

The POS rail is the checkout system for internal services. It creates a request, binds it to the merchant, and settles only after the signed transfer arrives.

Launch Readiness

Dark Coin is close to public shape, but full public launch still depends on trust and ops gates outside the frontend.

Already visible

Live domain, route hardening, reserve visibility, protected lanes, DRK trust proof, and the DRK / wL6ETH split are already visible publicly.

Still required

Verified contract source, treasury multisig, registrar and DNS hardening, liquidity proof, and external trust signals still matter before a full public push.

Best rollout path

Controlled beta, stress test, exploit and UX cleanup, then public announcement is the practical release order.

Phase 1

Small monitored beta group.

Phase 2

Settlement and wallet stress testing.

Phase 3

Exploit review and UX tightening.

Phase 4

Broader public launch after trust checks line up.