ChartRunner Public SDK Boundary

ChartRunner is a playable chart game and SDK prototype. This public documentation covers the demo, the SDK intent boundary, and devnet proof. Private execution, hosted agents, premium data, and strategy-heavy operating plans are intentionally excluded.

The core invariant is simple: every trade-like action moves through ChartRunnerSDK. Game controls, bots, widgets, and UI affordances may create intents; they do not bypass risk, wallet, broker, or approval boundaries.

Overview

ChartRunner turns trading primitives into game mechanics. A player can learn brackets, OCOs, ladders, hedges, alerts, and risk rescue flows by using them inside a chart game. The public build is meant to prove the feel, the product shape, and the security boundary.

Playable demo

Single-file browser prototype with chart movement, tools, campaign flow, and paper/sandbox primitives.

SDK shape

One intent path for order-like actions, ready to be backed by approved adapters when deliberately released.

Devnet proof

Public Anchor programs demonstrate maps, profiles, run records, oracle-shaped proof, and match-state proof.

Gated edge

Execution adapters, hosted bot transport, private data, and monetization operations stay outside the public repo.

Public Surfaces

Surface	Path	Public role
Landing	`/`	Project overview and live demo entry
Game	`/play/`	Playable chart game prototype
Wallet bridge	`/solana-connect/`	Explicit wallet and devnet handoff
Anchor source	`anchor/programs/`	Public program source and IDLs
Boundary docs	`docs/SDK.md`, `docs/PUBLIC_BOUNDARY.md`	What is public, what is gated, and why

SDK Boundary

The public SDK story is a contract, not a package promise. The game demonstrates the call shape and product rules; the standalone package remains gated until it is stable, documented, tested, and intentionally published.

game input
  -> ChartRunnerSDK intent
  -> risk and approval boundary
  -> paper/devnet result now
  -> approved adapter result later

Public examples should describe trade intents, paper fills, sandbox behavior, and wallet-approved handoff. They should not publish venue routing logic, private transport URLs, fee mechanics, bot operating instructions, or partner submission playbooks.

Devnet Programs

Program	Address	Public job
`chartrunner_maps`	DbzEqKfg...3UvH	Map hash/index proof
`chartrunner_registry`	ER8G9Bnv...rdcn	Profiles, run records, marketplace-shaped records
`chartrunner_oracle`	4vfZVDfD...i5wH	Price certificate proof boundary
`chartrunner_match`	3mzEAWZV...p5zu	Match-state proof boundary

Gated Systems

The public repo should not include the project edges that create durable economic value before they are ready to be sold or released.

Standalone SDK package source and generated browser artifacts.
Live execution adapters, routing preferences, production RPC choices, and venue-specific setup.
Hosted bot/agent transports, bridge URLs, private event streams, and operations logs.
Private replay data, backtest corpora, signal tuning, and model evaluation logs.
Partner submissions, sponsorship strategy, revenue mechanics, and token/economy operating plans.

Verification

Run the leakage guard and prototype syntax checks before public deploys.

node scripts/check_public_leakage.mjs
node scripts/test_public_leakage_guard.mjs
node /Users/julianroy/.agents/skills/chartrunner-playtest-verifier/scripts/check-prototype-js.mjs ChartRunner_Prototype.html