Schedule or defer §10.6.3 timeline windows (katrix-timeline) #95
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Review finding: unroadmapped spec MUST — fell through the milestone cracks. D23 narrowed katrix-timeline to windows + diffs '(M3)'; M3 closed without a window criterion; M6 lists only thread timelines; the deferred table lists only the identity-server API. §10.6.3 MUSTs (Timeline handle with subscription-bounded residency, updates flow of snapshot+diff, ItemContent sealed hierarchy, stableId across echo/decryption, CR-16 timeline half) are unbuilt. Live evidence: samples/demo RoomTimeline.kt:49 hand-rolls 'the glue the §10.6.3 window module will subsume'; docs/benchmarks/2026-08-cold-start.md:82 defers an NFR-3 re-check to 'when windows land in M3'.
Roadmap decision needed (precedence rules 2/4): pull into M6 as a criterion, or add to the deferred table with a reconsider-when trigger.