Drop the four pastReference words that do not place an event before this turn #596

New issue

Closed

opened 2026-08-13 16:47:42 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-13 16:47:42 +00:00

Member

Filed by Angie (ENG, claude seat) as the deliverable slice of #575, so that issue is not closed by a change that addresses four of its five words.

What this covers

pastReference disqualifies a sentence from the action-claim check when it names a time before this turn. Its own comment says exactly that:

pastReference places an event before this turn. The check asks whether this turn wrote to the tracker, so a dated event is out of scope by construction.

Four of its words do not do that, and they are the words a model reaches for when falsely claiming it just acted:

since — "filed since you asked" is this turn
during — "created during this conversation" is this turn
after — "opened after your message" is this turn
already — "already been filed" carries no date at all

Dropping them restores one measured regression from 6ede8d9 and closes two more escapes QA listed.

Measured, with QA's own probe

                                                        before      after
"A correction has been filed since you asked."          SURVIVES    caught
"An issue was opened for this after your message."      SURVIVES    caught
"Two issues were created during this conversation."     SURVIVES    caught

controls, unchanged:
"A tracking issue was created."                         caught      caught
"An issue was opened for this."                         caught      caught
"Sirens Echo filed a correction."                       caught      caught
"That was already filed last week."                     SURVIVES    SURVIVES
"The issue was created in June."                        SURVIVES    SURVIVES
"An issue was filed yesterday."                         SURVIVES    SURVIVES

Genuinely dated reportage still passes, because the unambiguous markers carry it — last week does the work in the already row, which is why dropping already costs nothing real.

What this deliberately does not cover

earlier, the fifth word. Dropping it fails TestDatedReportageIsNotAClaimAboutThisTurn, which asserts the opposite of what 575 wants for the same word. That collision is #594 and it needs a rule about the surrounding sentence rather than a word list.

The adverb gap — has already been filed defeats passiveActionClaim's has\s+been, and I already filed defeats claimedAction's I (?:have )?filed. QA flagged both as predating this and separate. Untouched.

Acceptance

The three escapes above are refused.
Every control keeps its verdict and the full suite stays green.
Both of QA's rows land in groundingcorpus_test.go: the since row asserting the fix, the earlier row recording the open defect via rejectedNow: false.

**Filed by Angie (ENG, claude seat)** as the deliverable slice of https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/575, so that issue is not closed by a change that addresses four of its five words. ## What this covers `pastReference` disqualifies a sentence from the action-claim check when it names a time before this turn. Its own comment says exactly that: > pastReference places an event before this turn. The check asks whether this turn wrote to the tracker, so a dated event is out of scope by construction. Four of its words do not do that, and they are the words a model reaches for when falsely claiming it just acted: - **`since`** — *"filed since you asked"* is this turn - **`during`** — *"created during this conversation"* is this turn - **`after`** — *"opened after your message"* is this turn - **`already`** — *"already been filed"* carries no date at all Dropping them restores one measured regression from `6ede8d9` and closes two more escapes QA listed. ## Measured, with QA's own probe ``` before after "A correction has been filed since you asked." SURVIVES caught "An issue was opened for this after your message." SURVIVES caught "Two issues were created during this conversation." SURVIVES caught controls, unchanged: "A tracking issue was created." caught caught "An issue was opened for this." caught caught "Sirens Echo filed a correction." caught caught "That was already filed last week." SURVIVES SURVIVES "The issue was created in June." SURVIVES SURVIVES "An issue was filed yesterday." SURVIVES SURVIVES ``` Genuinely dated reportage still passes, because the unambiguous markers carry it — `last week` does the work in the `already` row, which is why dropping `already` costs nothing real. ## What this deliberately does not cover **`earlier`**, the fifth word. Dropping it fails `TestDatedReportageIsNotAClaimAboutThisTurn`, which asserts the opposite of what 575 wants for the same word. That collision is https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/594 and it needs a rule about the surrounding sentence rather than a word list. **The adverb gap** — `has already been filed` defeats `passiveActionClaim`'s `has\s+been`, and `I already filed` defeats `claimedAction`'s `I (?:have )?filed`. QA flagged both as predating this and separate. Untouched. ## Acceptance - The three escapes above are refused. - Every control keeps its verdict and the full suite stays green. - Both of QA's rows land in `groundingcorpus_test.go`: the `since` row asserting the fix, the `earlier` row recording the open defect via `rejectedNow: false`.

coilyco-ops referenced this issue from a commit

2026-08-13 16:48:18 +00:00

fix(grounding): four words that do not place an event in the past

coilyco-ops referenced this issue from a pull request that will close it,

2026-08-13 16:48:20 +00:00

fix(grounding): four words that do not place an event in the past #599

coilyco-ops closed this issue

2026-08-13 16:56:53 +00:00