Daneel

Context

Daneel trades US equities on paper. Indicator rules, sliding windows, opening-range breakouts, and AI-driven picks each run their own portfolio, evaluated every minute of the session. Decisions become order intents, guarded and routed to an Interactive Brokers paper account, and fills settle back into the strategy ledger exactly once. After the close, a post-mortem reviews the day. The point is to learn which strategies earn before any capital is at risk.

What we built

The product end to end, and this public desk: a landing page that reads from the same Firestore the dashboard does, so the strategies on the board, the equity, and the research notes are live, not sample data.

The numbers come from the ledger

Under the hero the page shows what is actually running: the strategies holding a position or a non-zero P&L, best equity first; paper equity across every ledger; the win rate from the latest post-mortem. If no review has been written yet, the section says so instead of faking one.

How it works, in four moves

Define the strategy. Evaluate every minute. Submit through the broker. Settle exactly once. Each move gets a paragraph and three proof points, and the proof points are the engineering: compare-and-set on every tick save, one Firestore transaction per settlement, pattern-day-trade and buying-power guards that fail closed.

Why it exists

Daneel exists because an audit showed where paper P&L lied. Everything since is designed so the ledger cannot flatter you: exactly-once settlements, guards that fail closed, paper first with live behind two flips, one portfolio per strategy, and broker fills in place of the zero-slippage paper fills that once created phantom equity.

Research you can read

A pre-market scan, a daily post-mortem, and scheduled research notes, written by Claude and kept display-only. They inform you, they never trade. The notes expire on their own and the next run writes fresh ones. The footer says the rest in four words: paper trading, not advice.

Under the hood

Next.js and React on Vercel, with server-only loaders reading Firestore through the Admin SDK so server and client render identically. Firebase Auth with session cookies, Cloud Functions for the scheduled ticks and agents, Interactive Brokers for paper execution, a Python signal engine for the indicators, and Framer Motion for the reveals.