Delivered: Stable history message ids, cache write elision, and first test target #19

Closed
opened 2026-08-22 04:17:11 +00:00 by kayg · 0 comments
Owner

Current state

Delivered in commit b944320. History projections derive deterministic v5-style UUIDs from session id, role, text, and an occurrence counter; live streaming messages retain random ids until the next history projection. Cache writes are elided when the sorted-key encoded transcript is byte-identical, the cache version was bumped, and the first test target covers identity, projection repeatability, write elision, and version rejection.

Acceptance criteria

  • Reprojecting the same history yields the same id for each row.
  • Repeated messages remain distinct through the occurrence counter.
  • Live delta updates do not change their row id during streaming.
  • Byte-identical cache writes are skipped and old cache versions are rejected.
  • The first test target exercises these contracts without touching the real cache.
  • The delivered behavior is represented by commit b944320.
## Current state Delivered in commit `b944320`. History projections derive deterministic v5-style UUIDs from session id, role, text, and an occurrence counter; live streaming messages retain random ids until the next history projection. Cache writes are elided when the sorted-key encoded transcript is byte-identical, the cache version was bumped, and the first test target covers identity, projection repeatability, write elision, and version rejection. ## Acceptance criteria - Reprojecting the same history yields the same id for each row. - Repeated messages remain distinct through the occurrence counter. - Live delta updates do not change their row id during streaming. - Byte-identical cache writes are skipped and old cache versions are rejected. - The first test target exercises these contracts without touching the real cache. - The delivered behavior is represented by commit `b944320`.
kayg 2026-08-22 04:17:15 +00:00
  • closed this issue
  • added the
    delivered
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/hermternal-apple#19
No description provided.