Article
One Rule, Three Ways to Trade It: From an Exported Level to an Order
A written rule is not a trade. Here is the same rule, taken from a real export, reaching the market three ways: by eye, as code you write, and handed to an AI agent.
The capture side, The MyLinedChart Loop: Mark Up, Name It, Export, Then Reopen It Next Session, ends with a rule written down: a price, a direction, and what invalidates it. That sentence still has to reach the market. There are three ways it does, and the export is what makes all three possible, because a rule you can read is a rule you can act on, alert on, or hand to something that writes code.
The Rule, and Where It Came From
In the sample export, NVDA carries a level named October High Break at 212.30 and a note reading stop-in long above 212. Written as a rule, that is one sentence.
A close above 212.30 is the trigger. Below the level is the invalidation. That is the whole rule, and every route below starts from that exact number, because it is in the file rather than in your head.
| Part of the rule | Value | From |
|---|---|---|
| Trigger | close above 212.30 | The exported level |
| Direction | long | The exported note |
| Invalidation | below 212.30 | The level, read the other way |
Route One: By Eye
The oldest way, and still the most common. You know the number, you watch the chart, and you act when price closes above it.
This is not a lesser route. Most traders run most of their rules this way, and the only thing the export adds is that the number you are watching for is the exact one you wrote down, not one you half-remember. When the level broke on 27 April at 216.54, a trader watching for a close above 212.30 had a clean, unambiguous signal.
Route Two: As Code You Write
If you run rules in a platform or a script, the exported rule is already most of the way to a condition. The level is a number; the trigger is a comparison.
In Python, C++, or whatever you use, the rule is a few lines. The point is not the syntax. It is that you are transcribing a value you exported, not eyeballing one off a chart image.
| The rule | As a condition |
|---|---|
| Long on a close above the level | if close > 212.30: signal = “long” |
| Invalid below the level | if close < 212.30: signal = None |
Route Three: Handed to an AI Agent
If you would rather not write the code, the export is exactly the input an AI agent needs. Claude Code, Codex, or your preferred agent reads the structured rule and drafts the condition for you, in the language you name (AI-Assisted Rule Drafting to Broker API Deployment: Codex + Claude Workflow for Traders walks the deployment side).
The reason this works is the same reason the other routes work: the rule left the chart as data. An agent cannot code a level it has to read off a picture; it can code one that arrives as “October High Break, 212.30, long above”. You still review what it writes and you still place the trade.
Where MyLinedChart Stops
All three routes end with you placing the order. MyLinedChart is read-only: it takes your analysis as far as a written, exportable rule and no further. It never sends, modifies, or cancels an order.
That boundary is the point, not a limitation. The rule is yours, the trade is yours, and the tool’s job is to make the rule precise enough that any of the three routes can act on it without guessing.
- By eye: you watch and act.
- As code: you write and run it in your own platform.
- Via AI: the agent drafts, you review, you place the trade.
FAQ
Is this telling me the 212.30 rule was a good trade?
No. This is about how any written rule reaches the market, using one real example. Whether a rule is worth trading is your judgement, not the tool’s.
Does MyLinedChart place the trade in any of these routes?
No. It is read-only in every case. You place the trade by eye, in your platform, or after reviewing what an agent wrote. It never touches an order.
Why does the export matter if I trade by eye anyway?
Because the number you watch for is the exact one you wrote down, months later if need be, instead of a level you redraw from memory.
What does the AI actually receive?
The structured rule: the named level, its price, the direction, and the invalidation. It codes from that, which is why the export is what makes the AI route possible at all.
Sample Structured Chart-Data Exports
Review how chart drawings, annotations, OHLC, volume, and execution context become reusable structured data.