Expand description
Where a session title is stored, and when a new one replaces the old.
Both writers go through store_title: the pane’s own request
(session:activity_summary, on a human message) and the empty-title recovery
sweep (backend::reactive::activity_watcher). The check and the write happen
in one transaction, so neither can overwrite a title the other stored while
its call ran. The pane used to write the title itself, after its own copy of
these rules. docs/reports/REPORT_AMBIENT_FRAMEWORK_REASSESSMENT_2026_10_08.md
section 6.7.
Enums§
- Replace
- When a candidate title is stored.
Constants§
- META_
TITLE - The block meta key the title lives in. The pane header and the Swarm row read it.
- NEWS_
MAX_ 🔒OVERLAP - Below this overlap (Jaccard over topic words) a new title counts as news.
- STOP_
WORDS 🔒 - Words that carry no topic, ignored when comparing two titles.
Functions§
- is_
title_ news - Is
candidatea different goal fromcurrent, or a rewording of it? A rewording (“Fix the login race” → “Fix login race condition”) keeps the old title; a real change of topic replaces it. - store_
title - Store
titleas the block’s session title ifreplaceallows it. A value that is not a usable title is never stored.still_currentis asked inside the transaction: a request superseded by a newer one must not store its title after the newer one did.Ok(true)when written. - topic_
words 🔒