Skip to content

Populate tool_events distance-to-human columns - #8

Merged
MPIsaac-Per merged 1 commit into
mainfrom
improve/tool-event-distances
Aug 5, 2026
Merged

Populate tool_events distance-to-human columns#8
MPIsaac-Per merged 1 commit into
mainfrom
improve/tool-event-distances

Conversation

@MPIsaac-Per

Copy link
Copy Markdown
Owner

Rectifies the three items deferred from v0.1.1.

  • tool_events now computes the four documented distance columns instead of leaving them NULL: session-row distances to the nearest human message on each side, and 1-based tool positions within the run between two human messages. NULL when no human message exists on that side.
  • Ingest header documents the confusing Binder Error a zero-byte or non-conforming glob produces.
  • RELEASING documents the SSH tag-signing configuration; v0.1.0 and v0.1.1 predate it and stay unsigned.

Verified with a new regression test on the shipped fixture plus a denser synthetic session (two humans, four tool events across three assistant turns) checked against hand-computed expectations. 27 tests pass; ruff/format clean.

Metric note: the four columns previously carried NULL, so any consumer that filtered on them now sees values for the first time.

🤖 Generated with Claude Code

The schema documented distance_from_previous_human_message,
distance_to_next_human_message, tools_since_previous_human, and
tools_until_next_human, but the ingest hardcoded all four to NULL.
Compute them from the nearest human message on each side of every tool
event, document the zero-byte-glob Binder Error in the ingest header,
and record the SSH tag-signing setup in RELEASING.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@MPIsaac-Per
MPIsaac-Per merged commit 52c39b2 into main Aug 5, 2026
6 checks passed
@MPIsaac-Per
MPIsaac-Per deleted the improve/tool-event-distances branch August 5, 2026 14:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants