Skip to content

docs: tell the framework story in the README - #1192

Open
bennycode wants to merge 1 commit into
feat/graph-builder-uifrom
docs/readme-framework-story
Open

docs: tell the framework story in the README#1192
bennycode wants to merge 1 commit into
feat/graph-builder-uifrom
docs/readme-framework-story

Conversation

@bennycode

Copy link
Copy Markdown
Owner

Stacked on #1191 (→ #1190#1189). Merge those first; GitHub retargets automatically. The hero image links to /graph-builder, which ships in #1191.

Why

The README read like a package index. What this repo can actually claim — and no other TypeScript project currently can — is a full loop: build a strategy visually or in code → prove it in a backtest that mirrors live execution → run the same object against a real broker. The README now leads with that story.

What changed

  • Hero screenshot of the Visual Strategy Builder (.github/images/strategy-builder.png), linked to the live page
  • "From idea to live trading in three steps" section: build (blocks or code, with side-by-side snippets), prove (backtest parity incl. the lookahead guard), run live (same code path + Telegram control) — closing with the equivalence guarantee
  • Highlights, Quickstart, packages table, and mermaid diagram updated to cover strategy graphs and the builder
  • Everything factual is backed by shipped code and tests in the stacked PRs — no aspirational claims

Lead with the idea-to-live-trading narrative instead of a package index:
build a strategy visually or in code, prove it in a backtest that mirrors
live execution, run it unchanged against a real broker. Adds a hero
screenshot of the visual strategy builder and updates highlights,
packages, and the architecture diagram to cover strategy graphs.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The README’s hand-written strategy example references types that aren’t imported, so the snippet won’t type-check when copied.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Updates the repository README to lead with the “full loop” framework narrative: build a strategy (visually or in code), validate it via backtesting that mirrors live execution, and run the same strategy object live through a broker + Telegram control.

Changes:

  • Adds a hero image and a “From idea to live trading in three steps” section describing the visual strategy builder, GraphStrategy, and backtest/live parity.
  • Updates Highlights, Quickstart wording, packages table, and the mermaid diagram to include the strategy graph/builder components.
  • Refreshes wording to emphasize equivalence guarantees between backtests and live trading.
File summaries
File Description
README.md Reframes the README around the visual strategy builder + graph strategies + backtest/live parity story, and updates highlights/diagram accordingly.
Review details
  • Files reviewed: 1/2 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread README.md
Comment on lines +25 to +29
import {Strategy} from 'trading-strategies';

// …and so is a hand-written class: return an OrderAdvice per candle, the framework owns the rest.
class MyStrategy extends Strategy {
protected async processCandle(candle: OneMinuteBatchedCandle, state: TradingSessionState) {
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants