What's pending across every project
4 open · sorted by priority then due-date
Filtered by tag data clear
todo
urgent
Live predictions are worse than "price stays the same" and ~50% on direction — fix before selling predictions
DB query 2026-10-19, last 30 days, slice 24 (2h ahead), all coins except TON: model error is ~2x the naive no-change baseline (BTC 0.555% vs 0.333%, ETH 0.868% vs 0.436%, DOGE 2.80% vs 0.71%), direction hit rate 49-51% (coin flip), and strong up-bias (DOGE predicts up 100% of the time, SOL/AVAX 89%). Also 2,489 predictions stored as NaN in 30 days. dbo.predictionvsactual is empty, so accuracy was never tracked. Retraining (#90) alone may not fix this — evaluate against the naive baseline in #115 and consider the model/target design.
#90#115dbo.<pair>_predictiondatadbo.predictionvsactual
CoinTrends.ai
· cointrends
· by saravanan@scrumclaw.ai
from the conversationsaravanan: I want you to access the database and query how the data looks like
claude: Compared 30 days of 2h-ahead predictions with actual prices: model error ~2x a no-change baseline, direction ~50%.
7d ago
10-19 14:07
10-19 14:07
todo
high
Extend ledger reconciliation migration to handle negative balances
Migration 0027 only inserts positive ADJUSTMENT entries when `wallets.balance > 0 AND gap.amount >= 0.01`. Users whose legacy wallets.balance is 0 (never populated) but who accumulated CHARGE entries end up with negative ledger balances and no automatic reconciliation.
Concrete case: saravanan.hp@gmail.com currently shows balance = -11152.52. Ledger has CHARGE entries but no matching TOPUP history was migrated in.
Options:
(a) Backfill missing legacy topups from external Razorpay reports before running the reconcile.
(b) Add a companion migration that reconciles from a manually-curated CSV of legacy balances.
(c) Add an admin credit tool + audit trail so support can fix these case-by-case.
Track down the actual topup history for affected users (query Razorpay payments API filtered by our account) and decide the right long-term reconciliation approach.
migrations/0027_wallet_ledger_balance_reconcile.up.sqlinternal/repositories/wallet_repo.go:30-48
Vajra Volt Mobile App
· vajra-mobile-app
· by saravanan@scrumclaw.ai
88d ago
07-31 02:51
07-31 02:51
note
DB snapshot 2026-10-19: what's fresh and what stopped
Fresh (5-min): pricedata (~518k rows/coin since 2024-10-29), indicators, marketindex, metalsdata, predictiondata, pricedatacache. Stopped: OHLCV Mar/Apr 2025; tradingrecommendation 2025-03-26; cryptonews & feargreedindex 2025-10-03; gainers/losers/trending 2025-10-13; updatetracking last 2025-01-30 (so the retrain baseline is 20 months old); TON price 2026-06-17. Empty: predictionvsactual, predictiontracking. Slice master has 24 slices per coin (5..120 min) all flagged active with modelfile set, but only slice 24 (120 min) models exist in GCS and are used. Legacy usertable 8 rows, paymentdetails 5 rows.
CoinTrends.ai
· cointrends
· by saravanan@scrumclaw.ai
from the conversationsaravanan: I want you to access the database and query how the data looks like
claude: Ran read-only queries via Cloud SQL export; summary of fresh vs stopped feeds.
💬 1 comment
7d ago
10-19 14:07
10-19 14:07
note
low
5 items captured in other session landed under project_id 'outputs' — orphans to clean up
The claude-collab session captured 1 decision + 4 todos on the GitHub integration, but they were stamped with project_id='outputs' because the plugin's cwd in that session was Cowork's outputs folder, not the project folder. The v3.4 ephemeral-folder guard prevents this for tracker_init_project but doesn't retroactively fix existing rows. Cleanup options: (a) DELETE FROM claude_projects WHERE project_id='outputs' CASCADE in Studio, accepting the loss of those originals (they're now duplicated under claude-project-tracker by this digest), or (b) UPDATE the 5 rows to set project_id='claude-project-tracker'.
claude-project-tracker
· claude-project-tracker
· by saravanan@scrumclaw.ai
137d ago
06-11 11:26
06-11 11:26