fix(investigation): the interview starts from the carrier, not over it#578
Open
leeovery wants to merge 1 commit into
Open
fix(investigation): the interview starts from the carrier, not over it#578leeovery wants to merge 1 commit into
leeovery wants to merge 1 commit into
Conversation
This was referenced Jul 27, 2026
Open
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:48
371c4cf to
9c857c3
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:49
bbad1ba to
46219ee
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:49
9c857c3 to
45a697d
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:51
46219ee to
c3bf69b
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:51
45a697d to
e575ca3
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:52
c3bf69b to
301e50c
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:52
e575ca3 to
823ab05
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:53
301e50c to
2bcfad6
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:53
823ab05 to
445ba54
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:54
2bcfad6 to
59e6967
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:54
445ba54 to
222919a
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:56
59e6967 to
0ff3350
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:56
222919a to
90c7074
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:57
0ff3350 to
5f44049
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:57
90c7074 to
41bd445
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:58
5f44049 to
7a33436
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:58
41bd445 to
e9c9a50
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:59
7a33436 to
ef6682b
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:59
e9c9a50 to
750408e
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 16:00
ef6682b to
e8e2840
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 16:00
750408e to
839ac1b
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 16:01
e8e2840 to
ff03d53
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 16:01
839ac1b to
d807b0c
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 16:02
ff03d53 to
b006d1e
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 16:02
d807b0c to
4e1b761
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 17:05
b006d1e to
84ade1a
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 17:05
4e1b761 to
6e99bc0
Compare
The guard fix beneath this made the symptom interview run for work shaped in discovery. The first walk through it showed what the arm does when it finally executes: three of six questions put back to the user things the carrier had already answered and initialisation had already written into the file — asking what the user sees when it crashes, against a Symptoms section already reading "No error surfaces to the user — the page just fails." That is what the prose literally said to do. The Otherwise arm loaded the question bank with no instruction to read the file it had just seeded, and the question bank has no such instruction either. The don't-re-ask rule lived in the entry skill; the process skill lost it at the handoff. The arm was unreachable for carrier-shaped work until the guard fix, so the gap has been there as long as the arm has — it just never ran. Step 3 now reads what the Symptoms section already holds before asking: the seed is the user's own account, questions go to what it does not answer, and thin answers get confirmed rather than re-asked. Found by the investigation-gathers-symptoms case two commits below, on its first run. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 17:06
84ade1a to
555d8f6
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 17:06
6e99bc0 to
610bf6a
Compare
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.
Summary
#575 made the symptom interview run for work shaped in discovery. The first walk through the arm showed what it does when it finally executes: three of six questions re-asked things the carrier had already answered and initialisation had already written into the file — asking what the user sees when it crashes, against a Symptoms section already reading "No error surfaces to the user — the page just fails."
That is what the prose literally said to do. The
Otherwisearm loaded the question bank with no instruction to read the file it had just seeded, and the question bank carries no such instruction either. The don't-re-ask rule lives in the entry skill ("Do not re-ask; live conversation context, when present, supplements the carrier"); the process skill lost it at the handoff.Pre-existing, newly reachable. The arm was effectively unreachable for carrier-shaped work until #575 fixed the guard, so the gap has existed as long as the arm has — it simply never ran on the path that matters.
Fix — three sentences ahead of the Load: read what the Symptoms section already holds (the seed is the user's own account), ask what it does not answer, confirm rather than re-ask where it is thin.
Provenance
Found by
investigation-gathers-symptoms(#576) on its first run — the walker put Q1 to a user whose file already contained the answer. One walk did this, the confirmation walk did not, which is exactly the model-dependent behaviour an unstated intent produces.Test plan
🤖 Generated with Claude Code
Stack