The terminal for agent-assisted trading
Agents built it.Agents maintain it.Agents run the brain.
Code still holds every limit and sends every order. You still decide.
- Calendar is confirmed for today.
- Your Standing Orders are armed. Signed by you.
- You said you would review your entry rule.
- Holding ‹n› alerts. None need you now.
May ask code to cancel resting entries on NQ.
The demo runs in this page only. ‹…› marks a placeholder.
2 Where we started
The hardest place to put an agent is next to an order button.
So we did not put one there. First we built the code around the button. Then we gave the agents more to think about. We never gave them the key.
3 What we built
Three jobs. Each with a line it cannot cross.
Agents built it.
Agents wrote it. Other agents tried to break it. A gate script decided whether the evidence passed. A person approved the change.
Still cannotmerge alone
Agents maintain it.
The Night Shift replays the failing day and tests each fix on recorded days. A person approves it.
Still cannotedit its own gate
Agents run the brain.
The Desk: Research, Market context, Journal and the Challenger, under a chief-of-staff coordinator. Every output is typed and source-linked.
Still cannotplace an order
4 Your day
A chief of staff beside you. Not a hand on the button.
- Before the openPrepares
Your Standing Orders are loaded. Only you change them.
- The openBriefs
Brief is ready. A line with no source is not printed.
- The sessionWatches
Holding ‹n› alerts. None need you now.
- A recipe firesDrafts
Ticket ready. On paper. The tap is yours.
- The countdownChallenges
One objection. It can shrink. It cannot add.
- After the closeRemembers
Day Book drafted from the record. A draft until you sign.
- Next morningFollows up
You said you would review your entry rule.
- Every timeYou decide.
Agents do reach you through what they put on screen. So every line is source-linked for you to check, and the code's checks do not depend on anything an agent wrote.
Phone, voice and menu bar can read, skip, lower and stop. They cannot arm or raise.
5 The bad day
On a bad day, it says the hard thing once.
In March you wrote: “After two losses, I stop for the day.” That is now.
Your own words, once. The limit in code was never up for debate.
Can't see NQ prices. The venue last confirmed your stop. Not taking entries.
An agent lost its lease. Running with models off.
Late, malformed or out of scope: the lease ends at once.
6 Observability
It watches itself, too.
- Received‹n› ms
- Validated‹n› ms
- Deduplicated‹n› ms
- Stamped‹n› ms
- Used in stance‹n› ms
Traceticket ‹id› ← stance ← stamped bar ‹id› ← NQ bars
- Offered
- ‹n›
- Taken
- ‹n›
- Skipped
- ‹n›
- Blocked
- ‹n›
- R per trade
- ‹R›
- Slip
- ‹n› ticks
- Cost of delay
- ‹R›
- Tier changes
- ‹n›
◇ Challenger has one too: objections upheld ‹n›, overridden ‹n›, late ‹n›.
Schematics on the synthetic sample fixture. The app measures. It promises nothing.
The Recipe Coach proposes. It never edits the recipe you are running.
Each night it writes one small change with its evidence. That becomes a new version in shadow, tested on recorded days and sealed holdout days. It moves up only on measured sessions and your sign-off.
- What-If ReplayAsk your past days a question. It answers in a ledger that cannot reach a venue.
- The GymHostile synthetic days each version must pass before it earns authority.
- The Flight RecorderWrites up any safety event from the record.
- The MeterA cost budget per agent, held by code. Over it, the agent is paused.
7 What did not change
A model still cannot place an order.
You can lend an agent a job. You cannot lend it a limit. Code caps every lease against a fixed policy no agent can edit. It ends on expiry, when you revoke it, or on Stop.