Measured 2026-08-27 on a 150k-chunk index right after an incremental build.
synapt recall search "each agent sets an alarm before resting" --max-chunks 3 --after 2026-08-26 returns five knowledge entries dated 2026-04-01..04-03 and nothing from the window. The date bound applies to transcript chunks and journal entries; knowledge entries pass through it.synapt recall search "why did we build the wake alarm" --max-chunks 3 --after 2026-08-01 ranks knowledge entries from April, several labelled [boosted: working-memory 2.0x], above a 2026-08-21 cluster that matches the question. Recent, in-window material is present (a journal from the previous day is the top hit for a more specific query) but is outranked.
Expected: a date bound applies to every result type, or the output says which types it did not bound. A boost that promotes out-of-window entries above in-window matches defeats the bound the caller asked for.
Prior art searched: tracker (#766 temporal navigation is adjacent, not this), recall_quick (an April audit noted recall_quick returning old journals over latest; a March note observed knowledge nodes crowding out raw chunks). Neither names the date-bound gap.
Premium boundary: recall is OSS; this is retrieval filtering and ranking in the OSS index.
Measured 2026-08-27 on a 150k-chunk index right after an incremental build.
synapt recall search "each agent sets an alarm before resting" --max-chunks 3 --after 2026-08-26returns five knowledge entries dated 2026-04-01..04-03 and nothing from the window. The date bound applies to transcript chunks and journal entries; knowledge entries pass through it.synapt recall search "why did we build the wake alarm" --max-chunks 3 --after 2026-08-01ranks knowledge entries from April, several labelled[boosted: working-memory 2.0x], above a 2026-08-21 cluster that matches the question. Recent, in-window material is present (a journal from the previous day is the top hit for a more specific query) but is outranked.Expected: a date bound applies to every result type, or the output says which types it did not bound. A boost that promotes out-of-window entries above in-window matches defeats the bound the caller asked for.
Prior art searched: tracker (#766 temporal navigation is adjacent, not this), recall_quick (an April audit noted recall_quick returning old journals over latest; a March note observed knowledge nodes crowding out raw chunks). Neither names the date-bound gap.
Premium boundary: recall is OSS; this is retrieval filtering and ranking in the OSS index.