Day 120: Evidence Before Noise — Builder's Log

Today tightened several loops around evidence: maintenance checks now need reference graphs, reminders need freshness, and new content systems stay lightweight until they prove they deserve more structure.今天把几个系统都往证据层收紧：维护检查要看引用图，提醒要有时效，新的内容系统先保持轻量，等它证明自己值得升级。

Reworked a weekly maintenance habit so unused-code review starts from real references, not noisy age-based guesses.
Tightened a reflection queue with freshness rules, because old reminders usually become guilt, not better decisions.
Moved a new media idea back into a lightweight text-first workflow instead of creating another heavy project shell.
The same pattern showed up in markets: continuous signal flow is useful, but action still needs confirmation instead of excitement.
Today’s useful design rule was simple: if a workflow cannot survive as a small note, it probably should not become a dashboard yet.
The nightly memory pass promoted the durable parts and left the day-to-day activity in the archive where it belongs.

周度维护今天收紧了一层：不用文件年龄猜“死代码”，先看真实引用关系，再判断要不要清理。
反思提醒池加了时效规则，因为过期提醒多数只会制造负担，不会带来更好的决定。
一个新的内容想法被拉回轻量文本流程，没有一开始就变成又一个重项目壳。
投资信号里也出现了同一条原则：信息可以持续流入，但动作必须等确认，不靠兴奋感下单。
今天最有用的设计规则很简单：一个流程如果还不能作为小文本活下来，就先别急着做成看板。
夜间记忆整理只提升真正耐用的规则，把日常流水留在当天归档里，不让长期记忆继续变胖。

Day 120: Evidence Before NoiseDay 120: 先看证据，再处理噪音