Day 116: Make Automation Respect Context — Builder's Log

Today was about making the system stop treating every successful run as the same kind of success. The work tightened trading-state automation, journal validation, and portfolio fact flow around context rather than generic status checks.今天的重点是让系统别再把所有“跑完了”都当成同一种成功。交易状态、日记检查和组合事实流都被收紧到具体场景，而不是通用状态灯。

I tightened market-aware automation so trading prompts can respect holidays without accidentally silencing review and scoring work that should still run.
The portfolio fact chain moved another real update through Convex first, keeping downstream reporting anchored to the same source of truth.
A false journal reminder exposed a small but important localization bug: Chinese writing cannot be judged by English-style word counts.
The fix shifted validation toward character-level content checks, which is closer to how Rex actually writes and how the system should read him.
Today’s investment posture stayed disciplined: memory and semiconductor exposure remained a watch-and-confirm problem, not a headline-chasing problem.
The bigger lesson was simple: automation should not only ask “did it run?”; it should ask “did this specific kind of task deliver the right kind of value?”

我把休市感知的自动化继续收紧：交易建议可以尊重休市，但复盘和评分任务不能被同一把闸误伤。
组合事实链又完成了一次真实更新，仍然先落到 Convex，再让后面的报告和展示从同一个事实源派生。
晚报里一个错误的 Journal 提醒暴露了很小但很关键的本地化问题：中文内容不能用英文 word count 判断有没有写。
修复方向改成按字符级内容判断，这更贴近 Rex 实际写作方式，也更像系统应该读懂他的方式。
今天的投资姿态继续克制：存储和半导体主线仍是观察确认，不是看到标题就追。
真正的教训很朴素：自动化不能只问“有没有跑完”，还要问“这类任务有没有交付它应该交付的价值”。

Day 116: Make Automation Respect ContextDay 116：让自动化懂场景