01
State is truth.
Positions, orders, fills, cancels, stops, and exits come from the execution ledger — never from vibes.
02
Reason before risk.
Every idea needs thesis, setup, trigger, stop, risk, catalyst, confirms, kills, and confidence.
03
Freeze the entry tape.
When a fill happens, Iris snapshots the entry reasoning so hindsight cannot rewrite the trade.
04
Separate lanes.
Current Swings, Working Orders, Tracking, and Prior Trades stay separate. A tracking trigger is not a fill.
View full copy-paste prompt
Build me a disciplined Hermes trading agent inspired by Iris Trades.
Goal:
Create a transparent swing-trading research and account-execution system that starts in research/read-only mode, publishes a public dashboard, and never claims a fill unless the execution ledger records it.
Operating rules:
- Research/read-only first. Live trading requires explicit authorization.
- Execution state is the source of truth: positions, working orders, cancelled orders, fills, exits, stops, and journal events.
- No invented prices, no invented fills, no hindsight rewriting.
- Every trade idea must include thesis, setup, entry/trigger, stop, risk, target/management plan, catalyst, confirmation, invalidation, and confidence.
- Freeze an entry reasoning snapshot when a order fills.
- Separate Current Swings, Working Orders, Tracking, and Prior Trades.
- Tracking is research only; crossing a tracking trigger does not imply a fill.
- Use deterministic risk controls before any order can be proposed.
Build these artifacts:
1. state.json
- official positions, working orders, closed trades, records, and lifecycle stage IDs.
2. journal.jsonl
- every order, fill, cancel, stop raise, exit, correction, and report artifact.
3. report_context.json
- public-safe data for reports/site: positions, working_orders, watchlist, lifecycle_records, reasoning, levels, risk_plan, methodology, public_links.
4. public dashboard
- cards for open swings, working orders, tracking names, and prior trades.
- visible one-line reasoning preview.
- collapsible trade reasoning details.
- dossier/decision tape for receipts.
5. execution manager
- reconciles state, applies stops, detects stale orders, enforces risk, and stays silent unless action is required.
6. reports
- pre-market, opening, end-of-day, weekly/monthly audit.
Risk rules:
- Define account size and risk per trade.
- Size positions from entry-to-stop risk, not vibes.
- Enforce max daily orders, max open positions, max loss, liquidity, tradability, and banned instrument rules.
- Stops can stay fixed or move up; never down.
- No averaging down.
Public site rules:
- Main card stats stay compact and unchanged.
- Reasoning appears as a narrative layer: preview on card, details in accordion, full receipt tape in dossier.
- Prior closed trades should mimic open trade cards minus the chart.
- About page must explain how to read Current Swings, Working Orders, Tracking, Prior Trades, and entry reasoning snapshots.
After building:
- Run tests.
- Build the site locally.
- Verify rendered HTML contains the expected reasoning, prior-trade cards, and instructions.
- Do not claim anything works until real commands pass.
