Title as claim exposes commitments, enabling Popperian maintenance
Type: note · Status: seedling
The title-as-claim convention is usually justified by its traversal benefit — links read as reasoning chains. But it has a separate, equally important benefit for maintenance: claim titles are Popperian. They declare what would make them wrong.
When your index is a list of topics ("memory notes", "linking thoughts"), reviewing it tells you nothing about what each note commits to. You must open the file to discover what it argues, and then decide whether you still believe it. Maintenance cost scales with the number of notes times the cost of loading each one.
When your index is a list of claims ("structure enables navigation without reading everything", "recognition not linking is the hard problem"), the review loop is cheaper. You can scan the list and ask of each title: do I still believe this? The ones that provoke doubt are the ones worth opening. The rest can be skipped. Maintenance cost scales with the number of doubtful claims, not the total number of notes.
This is Popper's criterion applied to knowledge management: a claim that can't be challenged can't be maintained. Topic titles hide their commitments; claim titles expose them. The maturation path in the discovery note is an example — it lists seven claims extracted from the note body precisely so each can be individually challenged and supported or refuted.
Relevant Notes:
- Title as claim enables traversal as reasoning — extends: adds the maintenance/falsification benefit to the traversal benefit already argued there
- Discovery is seeing the particular as an instance of the general — exemplifies: its maturation path is a list of claims extracted for individual challenge
- Mechanistic constraints make Popperian KB recommendations actionable — grounds: the Popperian framing that recommendations must be falsifiable to be useful
Distilled into:
- WRITING.md — the title-as-claim checklist item operationalizes this principle
Topics: