Say the idea. Read the rule before it runs.
Your sentence becomes a rule you can read and edit. Then it runs over the record as it stood at the time.
Your idea, in one sentence
- Signed in as
- —
- Plan
- —
- Runs a minute
- —
- Record covers
- read from the run
Nothing has been written yet. Writing the rule reads your sentence and nothing else; the run that follows reads the record and calls nothing.
—
Refused
We refused this backtest.
the field—
02
The rule, before anything runs
This is exactly what will run. Change anything you like and check it again — an edited rule skips that step entirely.
- When you may buy
- —
- Which companies
- —
- What sets it off
- —
- How long you hold
- —
- How you get out
- —
- Written by
- —
03
Result
- How early, on average
- —
- Trades before the news was out
- —
- What buying early adds
- —
| Version | You buy at | Return |
|---|
All three versions, in full
| Version | You buy at | Total return | Worst drop | Trades | Priced | Days in the market |
|---|
What we could and could not cover
| Ticker | Why it was left out | Filings | What that means |
|---|
Parts of the rule the record could not answer
| Part of the rule | What you asked for | Why it could not run |
|---|
Controls
| Control | What it takes away | Return | vs. real |
|---|
Where the numbers came from
- Dates covered
- —
- Records searched
- —
- Trading sessions
- —
- Calendar used
- —
- Tickers with prices
- —
- Prices pulled
- —
- Could a model have memorised this
- —
Run notes
An idea about options is tested here on the share price. We do not price premium, volatility or expiry, so what this answers is whether the move was still there at the moment you could have bought — not what to buy.
This card can’t be faked. One command checks it.
—
pip install git+https://github.com/sharath/pit-harness pit-harness verify-studio run.json
Save what the read-back below returns as run.json.
The command recomputes the fingerprint over the answer. It prints
RECEIPT OK when that matches the one above. That is how
anyone knows these numbers are the ones the engine produced. Change
one of them and it stops matching. Share the run and the same command
takes your link directly, with no key. It is the
checker, open source, running on
your machine.
Run this exact rule again
Make an API key on the dashboard.
Read this run back
The run is stored, so this reads the same answer back tomorrow, byte for byte — which is what the fingerprint is taken over. Reading your own run costs you nothing from your budget. Share it and the same request answers with no key at all; stop sharing and it goes back to answering “not found”.