Repository navigation
fix(inspect): T1 outcome signals and checkable first-episode config (v0.1.3) - #41
Merged
Merged
Conversation
…s loaded - The harness logs loaded instruction files just after the prompt - Only a first snapshot logged after a reply stays may-have-changed
- Code-computed end signals: open question, subagent started, revert, fixup, later episode - Outcome rules in the judge prompt use them; unknown only when none fits - Trimming keeps the last reply whole with its closing; middle replies cut first - Pack cap and Gate B estimate at 2.5 bytes per token, checked against measured calls
… excerpt cap - reverted, fixup_later, continued_later come from the linker flags, not the nearest links only - fixup_later and continued_later are weak links; only a revert makes reworked - Dropped work with no open question counts as abandoned - A questions list must be a heading or label line - Config excerpt up to 2,400 characters so four flagged turns keep their best lines
…ssage - Flagged middle messages and the first and last turns are cut only after instruction lines - continued_later counts a later episode on the same files within a day, as a hint - A redirect or taste choice no earlier text could cover is labelled the person's
- Matches how the episode cutter reads a question the agent moved past - The abandoned rule names started_agent as support for work still running
…ed_agent - Facts episodes carry no linker flags, so reverted and fixup_later read the stratum outcome first - started_agent could not tell a finished subagent from a running one, so it is gone - continued_later keeps the next episode of the same session: that is where an open question is answered
joshua-temple
changed the title
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
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.
TLDR
Why
Evidence
a snapshot logged right after the root turn, before any reply, is the config loaded for that promptend signals: computed by code from the last reply and later git and episode linksasksPerson: a question, lettered choices, or a questions list at the end; a plain report is nottrimming shortens middle replies first; the last reply keeps its full opening and closingconfig: four flagged turns with six best lines each all reach the judgeestimate: the per-call input estimate brackets measured calls, and stays honest at the larger capend signals: computed by code from the last reply and later git and episode linksover the cap, instruction lines go before the first message or a flagged message is cutchore(inspect): version 0.1.3; all tests passHow to Verify
cd inspect && npm test && npm run lint && npm run test:visualnode scripts/dry-run.mjs --require-node20history, Gate Byes; read the Outcomes line in the appendixshrine-inspect check-share