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 14:33
1e0a1d3 to
e179182
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:35
4139ab9 to
f8761f0
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:35
e179182 to
7b7407e
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:37
f8761f0 to
0ffba7e
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:37
7b7407e to
c99c099
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:40
0ffba7e to
22b8a74
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:40
c99c099 to
fbd915d
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:42
22b8a74 to
a3c9599
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:42
fbd915d to
95b4406
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:44
a3c9599 to
ff47bf2
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:44
95b4406 to
e021953
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:46
ff47bf2 to
4951384
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:46
e021953 to
e7270d6
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:48
4951384 to
25399f4
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:48
e7270d6 to
3051cc4
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:50
25399f4 to
cddac1a
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:50
3051cc4 to
f732013
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 14:52
cddac1a to
82fbe1e
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 14:52
f732013 to
6d6debf
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:43
82fbe1e to
36c196b
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:43
6d6debf to
e0b2e69
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:44
36c196b to
e4d2d05
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:44
e0b2e69 to
58bfb85
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:46
e4d2d05 to
bfb4571
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:46
58bfb85 to
371c4cf
Compare
leeovery
force-pushed
the
fix/prose-writes-are-evidence
branch
from
July 27, 2026 15:47
bfb4571 to
bbad1ba
Compare
leeovery
force-pushed
the
fix/investigation-no-reask
branch
from
July 27, 2026 15:48
371c4cf to
9c857c3
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 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
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