Repository map

What's implemented versus scaffolded across the Common Arcade monorepo.

  • apps/ — user-facing or network-facing deployables.
  • services/ — isolated workers for matches, policy, and builds.
  • packages/ — publishable standards, SDKs, runtimes, UI, and adapters.
  • schemas/, specs/, and rfcs/ — normative design artifacts.
  • infra/ — AWS, Vercel, and local deployment definitions.
  • tests/ — protocol, interoperability, load, chaos, and security suite placeholders.

What's real today

AreaStatus
apps/webPublic site, Studio, and the Fumadocs docs you're reading
apps/control-apiFull control plane — games, releases, projects, Studio, matches, Test Arena, Commons integration
apps/mcp-server14-tool MCP server (not yet published to npm)
apps/realtime-gateway + services/match-workerThe live match protocol and sandboxed rules host
services/payment-serviceHosted testnet paid matches (escrow settlement, public match records) and x402 paid analysis
packages/protocol, manifest, match-runtime, control-client, realtime-client, sdk, cli, studio, configTyped, tested, in active use
packages/contracts, economyArcadeEscrow contracts and deployments on Base Sepolia, Arc, Celo Sepolia, Hedera; economy adapter
packages/policy-ir, policy-runtime, team-policy, adaptation, test-arena, diagnostics, auth, conformance, observabilityReal, bounded implementations
examples/tic-tac-toe, examples/blackjack, examples/neon-duelWorking examples covering managed rules, payment demos, and browser/live documents
rfcs/0001, rfcs/0002Substantive, implemented-in-part RFCs (extensible capabilities; lobbies/series/remixes)
schemas/v0alpha1/11 versioned JSON Schemas served live from the control API

What's still scaffolding

AreaStatus
apps/match-supervisor, apps/registry-worker, apps/studio-orchestratorEmpty scaffolds — no durable ownership-lease supervisor or registry ingestion yet
services/build-worker, services/policy-workerScaffolds, no dependencies wired
packages/adapters/* (gymnasium, pettingzoo, nakama, agent-commons)stability: 'pre-v0alpha', implemented: false stub exports only
packages/react, packages/ui, packages/presentation-bridgeBoundary packages with minimal public surface so far
examples/duel, examples/football-arena, examples/swarm-tacticsREADME-only placeholders
tests/chaos, interop, load, protocol-vectors, securityREADME-only placeholders — actual tests live co-located as *.test.ts inside packages/apps instead
specs/Explicitly non-normative — only the two RFCs and the JSON Schemas are promoted so far

Every package still marked pre-v0alpha is a boundary, not a promise that its final API has been designed. See Architecture boundary for the control-plane/realtime-plane split, or the canonical system design document for the full decision record.

On this page