The present is only half
Browser exposes the tiered tree, frontmatter, links, and source note. It begins judgment but cannot finish it. A sentence that looks strange may deserve repair or preservation depending on why it exists.
Trail belongs beside the note. It shows when the sentence appeared and whether a semantic edit or an external drift sweep recorded it. Curation without provenance rewrites history from the appearance of the present.
History alone is insufficient
Many commits do not imply importance. A volatile working note may never enter boot while a once-written core principle is charged every session. Trail measures change; Weight measures recurring cost.
Weight needs file, folder, and vault totals plus the actual session boot chain. Compute from the loader's real order instead of guessing from folder names and creating another shadow contract.
The three views create questions for one another
A heavy file in Weight opens in Browser, then Trail explains when and why it grew. A repeatedly changed note in Trail opens in Browser for conflict and Weight for boot impact. No view replaces the judgment of another.
That connection is the core UX. A metric card should lead to evidence rather than Delete. The next user action becomes a better question before it becomes mutation.
Default order should support understanding, not alarm
Putting the largest file first in red implies that size is bad. Show scope and role, then let Weight sorting remain an optional lens. Default order is policy too.
Present source, active tier, owner, last semantic change, and token estimate together without collapsing them into one health score. A composite score destroys the explanations carried by different units.