Skip to content

Add build log and align remaining docs/scripts with the QQQ hourly re…#6

Merged
utkarshp845 merged 1 commit into
masterfrom
claude/alpaca-bot-strategy-revamp-feecee
Jul 12, 2026
Merged

Add build log and align remaining docs/scripts with the QQQ hourly re…#6
utkarshp845 merged 1 commit into
masterfrom
claude/alpaca-bot-strategy-revamp-feecee

Conversation

@utkarshp845

Copy link
Copy Markdown
Owner

…vamp

Swept the repo for leftover BTC-5m-default assumptions after the strategy revamp and fixed what was actually misaligned:

  • deploy/ec2/install_cron.sh: cron default was */5 * * * * (every 5 min) but every profile now trades hourly bars — changed to 5 * * * * (hourly)
  • docs/github_actions_ec2.md: still said "the deployed profile is BTC, 24/7 scheduling is correct" — no longer true now that spy/QQQ is the default
  • OPERATIONS.md: stale $250 paper equity (now $150 to match the real account) and a claim that BTC paper uses "larger sizing" than live (it's now an exact mirror by design); reordered examples to lead with the default equity profile
  • README.md: rewrote the opening description and Crypto section (still framed BTC as the always-on 24/7 default), replaced a "Deployment" section describing AWS ECR/IAM/run.sh/deploy.sh/a main branch — none of which exist in this repo — with a pointer to the actual GitHub Actions + SSH/ rsync path in docs/github_actions_ec2.md, dropped a risk-controls table row for REVERSAL_SIGNAL_STRENGTH_MIN (not read by any code, only test fixtures), fixed an orphaned bullet list missing its "Project Structure" heading, and updated the small-account sizing guidance to notional_cap
  • Added superseded banners to the two pre-revamp audit docs (strategy_audit_current.md, live_account_path_100usd.md) pointing at the new strategy doc, keeping their content as historical record

Added docs/BUILD_LOG.md as a running log for strategy/infra changes going forward, seeded with this entry and the prior QQQ revamp commit.

Verified: pytest (66 passed), bot.validate_runtime — docs/config/script changes only, no strategy logic touched.

…vamp

Swept the repo for leftover BTC-5m-default assumptions after the strategy
revamp and fixed what was actually misaligned:

- deploy/ec2/install_cron.sh: cron default was */5 * * * * (every 5 min) but
  every profile now trades hourly bars — changed to 5 * * * * (hourly)
- docs/github_actions_ec2.md: still said "the deployed profile is BTC, 24/7
  scheduling is correct" — no longer true now that spy/QQQ is the default
- OPERATIONS.md: stale $250 paper equity (now $150 to match the real
  account) and a claim that BTC paper uses "larger sizing" than live (it's
  now an exact mirror by design); reordered examples to lead with the
  default equity profile
- README.md: rewrote the opening description and Crypto section (still
  framed BTC as the always-on 24/7 default), replaced a "Deployment" section
  describing AWS ECR/IAM/run.sh/deploy.sh/a `main` branch — none of which
  exist in this repo — with a pointer to the actual GitHub Actions + SSH/
  rsync path in docs/github_actions_ec2.md, dropped a risk-controls table
  row for REVERSAL_SIGNAL_STRENGTH_MIN (not read by any code, only test
  fixtures), fixed an orphaned bullet list missing its "Project Structure"
  heading, and updated the small-account sizing guidance to notional_cap
- Added superseded banners to the two pre-revamp audit docs
  (strategy_audit_current.md, live_account_path_100usd.md) pointing at the
  new strategy doc, keeping their content as historical record

Added docs/BUILD_LOG.md as a running log for strategy/infra changes going
forward, seeded with this entry and the prior QQQ revamp commit.

Verified: pytest (66 passed), bot.validate_runtime — docs/config/script
changes only, no strategy logic touched.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@utkarshp845
utkarshp845 merged commit 3cef0b6 into master Jul 12, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant