feat(prose-tests): conduct — playing a person where a script cannot reach#576
Open
leeovery wants to merge 1 commit into
Open
feat(prose-tests): conduct — playing a person where a script cannot reach#576leeovery 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
feat/prose-conduct
branch
from
July 27, 2026 14:33
39f9f9b to
3bd3dad
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:35
b21db1d to
6672e48
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:35
3bd3dad to
47f09fd
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:37
6672e48 to
2ff5504
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:37
47f09fd to
67902ee
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:40
2ff5504 to
ffc3b16
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:40
67902ee to
63c4330
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:42
ffc3b16 to
e13466a
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:42
63c4330 to
054e015
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:44
e13466a to
8e8fc12
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:44
054e015 to
7cf7a7d
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:46
8e8fc12 to
d137a88
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:46
7cf7a7d to
8e9b00b
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:48
d137a88 to
3a72413
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:48
8e9b00b to
f19921b
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:50
3a72413 to
51289d6
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:50
f19921b to
dd831e7
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 14:51
51289d6 to
840a957
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 14:51
dd831e7 to
54c188a
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 15:43
840a957 to
efa86fb
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 15:43
54c188a to
5b8b106
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 15:44
efa86fb to
0299954
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 15:44
5b8b106 to
86be032
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 15:46
0299954 to
d4ba2c2
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 15:46
86be032 to
6cf217b
Compare
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 15:47
d4ba2c2 to
492bab7
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 15:47
6cf217b to
b2d60d2
Compare
…each A scripted answer covers a question with one right response. Some prose does not work that way: symptom gathering explores, and keeps exploring until it judges it has enough, so there is no fixed number of turns to script. Every case so far has stopped at the edge of such a stretch, which is why seven processing skills had no coverage past their gates. conduct is the third per-case input, beside answers and stubs: a description of the person on the other side, not a queue of replies. The walker answers as that person would, in their words, for as long as the prose keeps asking. A case may carry both — the script covers the discrete gates, the description covers the open stretches. Two guards keep it from becoming a back door through the P4 boundary. The template states it describes the user and never the walk: it cannot name an arm, end a step, or say what the prose ought to do. And the walker's standing instruction now says that playing the user is not steering the walk — a described user who would happily stop talking is still not permission to cut a loop the prose has not ended. The first case to need it walks investigation through its symptom interview: the fix in the commit below this one made the interview run, and this case is the one that fails on the prose before that fix — the finding landing twice, as the project requires. Its user is relaying the bug rather than living it: concrete about what they saw, plain about what they do not know, volunteering nothing past the question asked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
leeovery
force-pushed
the
fix/investigation-symptom-guard
branch
from
July 27, 2026 15:49
492bab7 to
232ea8a
Compare
leeovery
force-pushed
the
feat/prose-conduct
branch
from
July 27, 2026 15:49
b2d60d2 to
ec703d3
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
conductis the third per-case input, besideanswersandstubs: a description of the person on the other side, not a queue of replies. A scripted answer covers a question with one right response; symptom gathering explores until it judges it has enough, so there's no fixed number of turns to script. The walker answers as the described person would, in their words, for as long as the prose keeps asking. A case may carry both — the script covers discrete gates, the description covers open stretches.investigation-gathers-symptomswalks investigation through its symptom interview. Its claim 3 — the interview runs despite the carrier having populated Symptoms — is the claim that fails on the prose before fix(investigation): the symptom interview never ran for work shaped in discovery #575's guard fix, so the finding lands twice as CLAUDE.md requires. Its user relays the bug rather than living it: concrete about what they saw, plain about what they don't know, volunteering nothing.First run results
The case ran and did its job — 6/6 path steps including claim 3, all four deterministic checks, world PASS. It FAILed on one further claim whose evidence the harness truncates (an Edit response cut at 400 chars) — that's the next PR up the stack. It also surfaced the re-asking prose gap — the PR above that.
Test plan
🤖 Generated with Claude Code
Stack