A desk that grades its own homework.
Most research tools are a pipeline: something goes in, an answer comes out, and nobody keeps score. Flux is a loop. Every call carries the date it has to be right by, that date arrives whether the desk likes it or not, and the grade goes back to the analyst who made the call and weighs on what they file next.
This page is the honest version of how that works, including the parts that are not built.
Where it closes.
Five stations. Four of them are a pipeline; the fifth is what makes it a loop.
-
01
File
An analyst reads one name through one lens and files a prediction: a direction, a horizon, and the date it resolves. No date, no filing.
25 roles -
02
Weigh
A reviewer reads the filing against that analyst’s own graded record, and passes on only what they would take themselves.
10 roles -
03
Rule
The executive approves, cuts the size, or refuses. Refusals are written to the same log as approvals, with the gate that stopped them.
6 roles -
04
Act
What survives reaches a simulated execution desk and a paper account. There is no path from here to a real brokerage.
Paper only -
05
Grade
On the resolve date the call is marked against the tape, right or wrong, and the miss is kept in the same record as the hit.
5 roles
That last edge is the whole design. A desk that only publishes what it took is showing you a highlight reel; a desk that grades forward cannot quietly drop the calls that went against it, because the resolve date was written down before the outcome was known.
Read from the desk’s own record.
Forty-six specialists, and none of them work alone.
Information moves upward only. No branch hands work sideways or back down, and the analysts never see each other’s filings — agreement is only evidence if it was reached independently.
| Branch | Roles | What it does |
|---|---|---|
| Analyst | 25 | One name, one lens. Value, growth, catalysts, filings, options, macro, credit, the tape, and a red team whose job is to argue against the rest. |
| Review & strategy | 10 | Verifies the facts, re-derives the valuation, finds the undeclared macro bet, and ranks what survives against everything else competing for the same simulated capital. |
| Executive | 6 | Sets size, names the funding source, and rules. The risk officer’s veto cannot be overridden, and is expected to be used. |
| Monitoring | 5 | Tracks open positions against the thesis they were entered on, and flags a position being held for a new reason instead of the one it was underwritten on. |
The other roster.
A second set of specialists never touches a filing. They build and check the software you are reading this on.
102 build-side agents
Engineering, design, product, security, testing and project management, adapted from The Agency under the MIT licence. They review code, audit accessibility, hunt leaked credentials and catch layout regressions.
They are tooling, not product. Nothing they do reaches a member, and none of them can file, review or rule on anything. That work belongs to the forty-six above.
Every one carries the same rules
Agents share no memory with each other, so a constraint that lives in one place is a constraint nobody else knows about. The house rules are restated inside all 148 files.
- Inventing Never a number, a source, or a figure produced to make a panel look finished.
- Claiming No track record, no win rate and no backtest, because there is no replay engine to produce one.
- Labelling Anything simulated is marked at the figure itself rather than in a footnote.
- Absence Missing or stale data is reported as an output, not filled in with something plausible.
- Credentials Keys live in server configuration and never reach anything shipped to a browser.
What it runs on.
The front
- Pages Hand-written HTML and CSS over one shared stylesheet, with no framework and nothing to compile before it ships.
- Type Archivo, Public Sans and Azeret Mono, self-hosted, with metric-matched fallbacks so the page does not move when they load.
- Deploy Static hosting straight from the default branch, which puts a push live in under ten seconds.
The back
- Data Postgres, with the desk record in tables you can read through the same public views this page uses.
- Jobs Scheduled functions run the desk, mark the paper book, and grade predictions as they come due.
- Quotes One server-side path for every surface, so no market-data key is ever shipped to a browser.
- Models Claude for the analysts, reviewers and executive; a small in-browser approximation for short-horizon price shape, labelled as such wherever it appears.
What is not built.
A page about how something is made is worth very little if it only lists the parts that work. These are the gaps.
- Backtesting. There is no historical replay engine here, so you will not find a win rate on this site. The record is built forward instead, one dated call at a time.
- A track record. That forward record starts at zero and fills only as calls come due. Where it is still empty, the page says so rather than dressing the space.
- Real-money trading. Autopilot and the desk trade a simulated book, and connecting a brokerage does not change that. No real order is placed unless you confirm it yourself.
- Desktop and mobile builds. Flux runs in a browser today; the native clients are still being built, which is what the download page tells you.
- Customers, press and case studies. There are none of these, which is why none appear anywhere on the site.
Flux is research and automation software, not investment advice, and DSH Trading is not a broker-dealer. The Flux Fund is a simulated paper account using virtual money; results are hypothetical and do not represent real trading. Trading involves risk of loss, including loss of principal.