Conversation
`docs/ticket/` gains a record of what the coding-harness study at arXiv:2609.20804 establishes, how each of its three ablated components (planning, action space, context management) maps onto JP's turn loop, and a SWOT drawn from the comparison. Six proposal tickets follow from it and are linked from its closing section. The comparison's sharpest finding is that JP runs the `jp query` path with no context management at all: `jp_llm::window::truncate_to_fit` has two production call sites, `jp_llm::title` and `jp_cli`'s inquiry backend, and neither is the query path. `git log -S` confirms it arrived with the inquiry work and was never wired to `query`, so the absence is original rather than a regression. That gap is filed separately from the compaction proposal it surfaced, because it holds whether or not RFD D50 ever lands. The remaining proposals cover bounded tool output (promote RFD D24), staged elision before summarization in RFD D50, per-response token usage as a conversation event, a turn-scoped cycle cap with identical-call streak detection, and an open question about whether a plan belongs in conversation history. The usage ticket is ranked ahead of the tuning work it enables: JP records no token counts today, so every other proposal here is currently unfalsifiable. Signed-off-by: Jean Mertz <git@jeanmertz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/ticket/gains a record of what the coding-harness study at arXiv:2609.20804 establishes, how each of its three ablated components (planning, action space, context management) maps onto JP's turn loop, and a SWOT drawn from the comparison. Six proposal tickets follow from it and are linked from its closing section.The comparison's sharpest finding is that JP runs the
jp querypath with no context management at all:jp_llm::window::truncate_to_fithas two production call sites,jp_llm::titleandjp_cli's inquiry backend, and neither is the query path.git log -Sconfirms it arrived with the inquiry work and was never wired toquery, so the absence is original rather than a regression. That gap is filed separately from the compaction proposal it surfaced, because it holds whether or not RFD D50 ever lands.The remaining proposals cover bounded tool output (promote RFD D24), staged elision before summarization in RFD D50, per-response token usage as a conversation event, a turn-scoped cycle cap with identical-call streak detection, and an open question about whether a plan belongs in conversation history. The usage ticket is ranked ahead of the tuning work it enables: JP records no token counts today, so every other proposal here is currently unfalsifiable.