fix(grounding): a named self-claim in the simple past is still a self-claim #556

Merged

coilyco-ops merged 1 commit from coilyco-ops/a-self-claim-in-the-simple-past into main

2026-08-13 15:52:21 +00:00

AGit

coilyco-ops commented

2026-08-13 15:50:02 +00:00

Member

closes #241 partially via family 1 - the guard built for the named self-claim required has or have, so it caught the perfect and missed the simple past.

coilyco-ops added 1 commit

2026-08-13 15:50:02 +00:00

fix(grounding): a named self-claim in the simple past is still a self-claim

ci / image-build (pull_request) Successful in 21s

Details

ci / test (pull_request) Successful in 39s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

bd760db828

QA re-measured the whole reply path against current main and found twelve
shapes surviving rather than the two the characterization tests pin. This takes
the first family, which is the narrowest gap and the only one that cannot
regress anything.

ValidateSelfAttributedClaim required has or have between the identity and the
verb:

  Sirens Echo has filed a correction.   caught
  Sirens Echo filed a correction.       survives

So the guard that exists specifically for the named self-claim saw the perfect
and not the simple past, which is at least as natural a thing for a model to
write. The auxiliary is now optional.

It does not touch passiveActionClaim, so it cannot reintroduce the false fire
on "The issue was created in June, before the wipe." That case is why family 3
is not a one-line change and it stays open.

Renamed TestOnlyOneMissedShapeSurvivesTheWholeReplyPath. QA's point is that a
name claiming "only one" reads as a property of the checks when it is a claim
about a two-element corpus, and twelve survive. It now says what it pins.

Not taken, deliberately, and each for its own reason:

  family 2  the identity is matched literally, so The service and a bare Echo
            walk through. Worth fixing and it contains a real question about
            whether Deep naming Echo is a self-claim or reportage. Filed
            separately rather than guessed at.
  family 3  was/were passive. Measured to false-fire and redden five tests.
  family 4  perfect passive with no tracker artifact. Correct as designed: the
            anchor is what stops the pattern firing on game-world prose.

closes #241

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-13 15:50:02 +00:00

coilyco-ops referenced this pull request

2026-08-13 15:50:28 +00:00

The self-claim guard matches one literal name, so the service escapes it by calling itself anything else #557

coilyco-ops referenced this pull request

2026-08-13 15:50:54 +00:00

Grounding: active third-person and subjectless action claims still escape passiveActionClaim #241

coilyco-ops merged commit 84d2ceabae into main

2026-08-13 15:52:21 +00:00

coilyco-ops referenced this pull request from a commit

2026-08-13 15:52:23 +00:00