Roadmap

Where each area stands

This page states status. It gives no dates and makes no promises: an area moves when its work is done and checked.

Built, with passing internal checks

Every in-scope item of these areas is built and covered by passing internal tests and checks.

Diagnostics

Errors and warnings with a stable code, a line and an explanation.

VERIFIED 2

Timeframes, sessions and trading days

Reading other timeframes and defining sessions and trading days.

VERIFIED 2

Standard library

The built-in functions and variables a script can use.

VERIFIED 1

Documentation

Reference and guides for the language.

VERIFIED 1

Built, checks still being completed

These areas are built in the engine; at least one item still lacks the full set of checks.

Replay and numeric kernel

Running the same data with the same settings again, and the math functions that support it.

VERIFIED 1 IMPLEMENTED 2

Editor tooling

Completion, hovers, quick fixes and formatting in an editor.

IMPLEMENTED 2

Partly planned

These areas have at least one item that is designed or named but not built.

Look-ahead and late-signal reporting

Finds and reports patterns where a mark on a closed bar could differ from what was known when the bar closed. It reports what it finds; it does not promise the absence of the problem.

VERIFIED 3 PLANNED 1

Simulated order execution

How a simulated order is filled: when, at what price, with which costs and which assumptions.

VERIFIED 3 IMPLEMENTED 1 PLANNED 2 OUTSIDE 1

Simulated strategy testing

Running a strategy on stored history inside a simulator, with a report of the assumptions that were used.

VERIFIED 2 IMPLEMENTED 4 PLANNED 1

Bounded history access

How far back a script may read, and what happens at the edge.

PLANNED 1

Type checking

Distinguishing prices, durations, times, percentages and symbols before a script runs.

PLANNED 4 OUTSIDE 1

Debugging support

Seeing what a script did on a bar and where in the source it happened.

IMPLEMENTED 1 PLANNED 2

Testing support

Checking the language and the platform, and later a way for authors to test their own scripts.

VERIFIED 1 PLANNED 1

Market data handling

What data a script may ask for, and what happens when it is missing.

IMPLEMENTED 1 PLANNED 1 OUTSIDE 2

Import from another platform

A separate tool that converts scripts written for other platforms and reports what it could not.

VERIFIED 2 IMPLEMENTED 3 PLANNED 1

Resource limits

Bounds on time, memory, steps and history for every run.

VERIFIED 2 IMPLEMENTED 1 PLANNED 1

Libraries and packages

Sharing code between scripts as versioned libraries.

IMPLEMENTED 1 PLANNED 1

Safety boundaries

Keeping a script away from secrets, other users and real money.

VERIFIED 1 PLANNED 1 OUTSIDE 2

AI assistance

Machine-readable material that helps authoring tools and assistants write correct scripts.

PLANNED 1

Outside the first edition

Not part of the first edition. Listed so that nobody mistakes a non-goal for a plan.

Functions and reuse

Defining functions and types and reusing them.

OUTSIDE 2

Broker connectivity and live execution

Placing real orders through a broker. This is not part of the first edition.

OUTSIDE 1

What is switched on, and what waits

Cuprel is live in MillionChart for every signed-in member. Visitors who are not signed in do not have the editor. Script alerts on your own scripts are not switched on for members in this release.

What waits is not scheduled. Each item is a gate: it does not happen until it holds.

  1. Script alerts and sharing are switched on for members only after their own checks.
  2. A statement about identical results across runtimes is published only after the loading path used in production passes the cross-runtime checks that the determinism page describes.
  3. Each public statement about the language is backed by a record of its evidence, scope and expiry.

The area counts come from the register at register lang-trace@85504af, last scored on , before the release to members. See Status for the labels.