Status

What members can use, and what is not done

Cuprel is live in MillionChart for every signed-in member. Visitors who are not signed in do not have the editor. This page says what members can use, what is switched off, and how the items of the internal capability register are labelled.

Where you can use it

Availability today
Place or partToday
Script editor in MillionChartScripts are written in the chart under Indicators, On chart, My scripts: New script opens the editor, Save keeps the script with your account, and Add to chart runs it on the chart.
Your scriptsScripts are private to your account and, in this release, run in your browser only. Sharing is not available.
Script alerts on your own scriptsScript alerts on your own scripts are not switched on for members in this release.
Strategy LabMembers can test a strategy in the chart's Strategy Lab. On the free chart plan it has 10 runs a month on up to 92 days of history.
Source conversion from other platformsExperimental, a limited subset. See Import.
Live tradingNone: no live trading and no broker connection.
Tutorials and sample programs on this sitePublished in Learn.
PlaygroundNot published.
Command-line toolsDevelopment use only.

The internal capability register

64 design items are tracked in the internal capability register. The counts below come from the register at the revision register lang-trace@85504af, last scored on , before the release to members. It has not been scored again since. Its labels say how far each item is built and checked inside the project; they do not say what members can use. That is the table above.

The labels

VERIFIED
Built, and covered by passing internal tests and checks.
IMPLEMENTED
Built in the engine. The full set of checks is not complete yet.
PREVIEW
Something you can look at, marked as unfinished.
PLANNED
Designed or intended, not built. Never shown as available.
EXPERIMENTAL
Built to measure an idea. It may change or be removed.
OUTSIDE
Not part of the first edition. Listed so that nobody mistakes a non-goal for a plan.

How the register's words map to the labels

The internal register uses its own words. They map to the labels above like this, and the mapping is applied by a script, not by hand.

Register status and the label shown here
Register statusLabelMeaning
verifiedVERIFIEDBuilt, with passing internal tests and checks.
implementedIMPLEMENTEDBuilt; checks not complete.
architectedPLANNEDDesigned, not built. It is never shown as available.
absentPLANNEDNamed as a need, not designed yet.
Declined or out of scope for the first editionOUTSIDENot part of the first edition.

The register has no label that means available to members; what members can use is in the first table of this page. PREVIEW and EXPERIMENTAL are in the vocabulary and are not used by any item yet.

The totals

VERIFIED
21 items
IMPLEMENTED
16 items
PLANNED
18 items
OUTSIDE
9 items

By area

Each area shows the lowest label among its in-scope items: an area at PLANNED has at least one item that is only planned.

Capability areas, the lowest label among their in-scope items, and the counts
AreaLowest labelShareItems
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.
PLANNED VERIFIED 3 PLANNED 1
Simulated order execution
How a simulated order is filled: when, at what price, with which costs and which assumptions.
PLANNED 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.
PLANNED VERIFIED 2 IMPLEMENTED 4 PLANNED 1
Bounded history access
How far back a script may read, and what happens at the edge.
PLANNED PLANNED 1
Type checking
Distinguishing prices, durations, times, percentages and symbols before a script runs.
PLANNED PLANNED 4 OUTSIDE 1
Replay and numeric kernel
Running the same data with the same settings again, and the math functions that support it.
IMPLEMENTED VERIFIED 1 IMPLEMENTED 2
Debugging support
Seeing what a script did on a bar and where in the source it happened.
PLANNED IMPLEMENTED 1 PLANNED 2
Testing support
Checking the language and the platform, and later a way for authors to test their own scripts.
PLANNED VERIFIED 1 PLANNED 1
Diagnostics
Errors and warnings with a stable code, a line and an explanation.
VERIFIED VERIFIED 2
Timeframes, sessions and trading days
Reading other timeframes and defining sessions and trading days.
VERIFIED VERIFIED 2
Market data handling
What data a script may ask for, and what happens when it is missing.
PLANNED 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.
PLANNED VERIFIED 2 IMPLEMENTED 3 PLANNED 1
Resource limits
Bounds on time, memory, steps and history for every run.
PLANNED VERIFIED 2 IMPLEMENTED 1 PLANNED 1
Functions and reuse
Defining functions and types and reusing them.
OUTSIDE OUTSIDE 2
Libraries and packages
Sharing code between scripts as versioned libraries.
PLANNED IMPLEMENTED 1 PLANNED 1
Safety boundaries
Keeping a script away from secrets, other users and real money.
PLANNED VERIFIED 1 PLANNED 1 OUTSIDE 2
Broker connectivity and live execution
Placing real orders through a broker. This is not part of the first edition.
OUTSIDE OUTSIDE 1
Standard library
The built-in functions and variables a script can use.
VERIFIED VERIFIED 1
AI assistance
Machine-readable material that helps authoring tools and assistants write correct scripts.
PLANNED PLANNED 1
Editor tooling
Completion, hovers, quick fixes and formatting in an editor.
IMPLEMENTED IMPLEMENTED 2
Documentation
Reference and guides for the language.
VERIFIED VERIFIED 1

Outside the first edition

Edition 1 has no broker connectivity and no live execution. Live execution would be a separate product capability with its own review. These areas contain items that are outside the first edition:

  • Simulated order execution: 1 of 7 items
  • Type checking: 1 of 5 items
  • Market data handling: 2 of 4 items
  • Functions and reuse: 2 of 2 items
  • Safety boundaries: 2 of 4 items
  • Broker connectivity and live execution: 1 of 1 items