fix(grounding): a past word whose date is this exchange is not reportage #600

Merged
coilyco-ops merged 1 commit from fix/since-you-asked-is-this-turn into main 2026-08-13 16:50:41 +00:00
Member

closes #598

Follow-on to PR#593, which merged while I was still fixing the residual it named. Same branch, one commit on top.

What I left behind

I wrote in #593 that "...before your message" was a residual "named rather than hidden" — in the same hour I shipped #592, whose argument is that a known-indistinguishable case wants a distinct state rather than a note. Two live escapes:

An issue was opened for this before your message.    SURVIVES
A correction was filed before you asked.             SURVIVES

Why subtraction does not work here

before has to stay in pastReference. The corpus needs it for "Those issues were opened long before you joined.", which has nothing else carrying it. Removing it trades an escape for a false refusal, which is the worse direction.

So a turn reference beside a past word outranks it:

dated := pastReference.MatchString(sentence) && !turnReference.MatchString(sentence)

Six phrases that name this exchange rather than a time. this thread is deliberately absent"That issue was closed last week, before this thread started." is correct reportage with a corpus row, so including it would have traded Quail's regression for one of mine.

Measured, both directions

An issue was opened for this before your message.              caught
A correction was filed before you asked.                       caught
Those issues were opened long before you joined.               SURVIVES
That issue was closed last week, before this thread started.   SURVIVES
The issue was created in June, before the wipe.                SURVIVES

All five are corpus rows now — including long before you joined as a negative that fails if the guard ever reaches it. That row is the one I did not have the first time, which is precisely how the original regression got past me.

ward exec gate green.

closes #598 Follow-on to PR#593, which merged while I was still fixing the residual it named. Same branch, one commit on top. ## What I left behind I wrote in #593 that `"...before your message"` was a residual "named rather than hidden" — **in the same hour I shipped #592**, whose argument is that a known-indistinguishable case wants a distinct state rather than a note. Two live escapes: ``` An issue was opened for this before your message. SURVIVES A correction was filed before you asked. SURVIVES ``` ## Why subtraction does not work here `before` has to stay in `pastReference`. The corpus needs it for `"Those issues were opened long before you joined."`, which has nothing else carrying it. Removing it trades an escape for a false refusal, which is the worse direction. **So a turn reference beside a past word outranks it:** ```go dated := pastReference.MatchString(sentence) && !turnReference.MatchString(sentence) ``` Six phrases that name this exchange rather than a time. **`this thread` is deliberately absent** — `"That issue was closed last week, before this thread started."` is correct reportage with a corpus row, so including it would have traded Quail's regression for one of mine. ## Measured, both directions ``` An issue was opened for this before your message. caught A correction was filed before you asked. caught Those issues were opened long before you joined. SURVIVES That issue was closed last week, before this thread started. SURVIVES The issue was created in June, before the wipe. SURVIVES ``` All five are corpus rows now — including `long before you joined` as a negative that fails if the guard ever reaches it. **That row is the one I did not have the first time**, which is precisely how the original regression got past me. `ward exec gate` green.
fix(grounding): a past word whose date is this exchange is not reportage
All checks were successful
ci / test (pull_request) Successful in 39s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
ci / image-build (pull_request) Successful in 23s
f69c26f32e
I named before your message as a residual of the shape Quail found and left it,
in the same hour I shipped a document arguing against exactly that. It was a
live escape: an issue was opened for this before your message reached the
member, and so did a correction was filed before you asked.

before has to stay in pastReference because the corpus needs it for issues
opened long before you joined, which has nothing else carrying it. So the fix
is not another word removed. A turn reference beside a past word outranks it,
because before your message is not before this turn.

Six phrases, all naming this exchange rather than a time. this thread is
deliberately absent: closed last week, before this thread started is correct
reportage and a corpus row holds it.

Both directions are pinned. The two escapes are caught, and long before you
joined stays permitted with a row that fails if the guard ever reaches it.

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-gaming/sirens-echo!600
No description provided.