
What happened
On October 5, Claude Code spotted that one stock had 17 judgments where the invalidation level was hit on the very day of execution; that stock had done a 3-for-1 split on September 29.
Why it matters
yfinance returns past daily candles adjusted down to one-third after a split, while the prediction ledger keeps the original pre-split prices, so comparing them made the stock look like it crashed one-third instantly and triggered the invalidation judgment, according to the developer.
Summaries like this, every morning.
ALPHA FORGE is a personal project: a Japanese stock AI screening and continuous-learning terminal developed by one person together with Claude Code. Each morning the AI extracts candidate stocks and records them in a prediction ledger, storing only what was known at extraction time — the simulated entry price, the scenario invalidation level, and the expected range ceiling. Every evening, a settlement process compares those ledger prices with subsequent daily candles to see whether the entry filled and which of the invalidation level or the range ceiling was reached first.
The trouble surfaced on the morning of October 5, when Claude Code was checking the settlement numbers and noticed one stock behaving oddly: judgments showed the invalidation level being reached on the very day of execution. That stock had split one share into three on September 29. Because yfinance returns historical daily candles adjusted retroactively to one-third after a split — a common convenience so charts look continuous — the ledger's pre-split prices were being measured against post-split candles. The developer checked 24 other already-settled stocks and found no other discrepancies.
The repair keeps the ledger's recorded values untouched so the original morning's reasoning stays readable, and instead aligns the units just before comparison. Splits effective on or after the extraction day are multiplied into a cumulative ratio, and the three prices are divided by it; candles without a Stock Splits column, such as those from a backup data source, are left uncorrected. The 17 existing settlements were rewritten only after a full backup of the production database, with the resolved_at timestamps kept at their original times. The developer notes that because the numbers moved in a favorable direction, recording the changed count and the before-and-after values mattered all the more — a discipline the AI's instructions formalize as confirmation, backup, and a report of changed counts and values.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Anthropic released its S-1 on Monday targeting a valuation of around $2 trillion and disclosed $16.8 billion i…

OpenAI marked Day 19 of its 28-day update run on October 24, 2026, releasing Codex CLI 0.164.0 and changing Co…

On Day 13 of OpenAI's 28-day shipping event, Tibo Sottiaux announced a usage-limit reset for Codex and ChatGPT…

Anthropic's S-1 shows Amazon holds convertible notes with $6.2 billion in principal outstanding, valued at $97…

The CNBC page referenced in the feed carries only subscription and navigation text, not the reported story on…

Applied Materials is increasing its investment in BE Semiconductor Industries to around a 20% ownership stake…
