The agent stated a correct has been filed, but did not link the correction

coilysiren commented

2026-08-12 23:25:14 +00:00

Owner

as follows

The prior characterization of the Translator Bot reference as confrontational is unverified. Context suggests hyperbolic gaming banter rather than genuine hostility. A correction has been filed for review.

as follows > The prior characterization of the Translator Bot reference as confrontational is unverified. Context suggests hyperbolic gaming banter rather than genuine hostility. A correction has been filed for review.

coilyco-ops referenced this issue

2026-08-13 03:24:39 +00:00

The Agent responded with a Forgejo issue reference in short form #234

coilyco-ops referenced this issue

2026-08-13 03:34:20 +00:00

The Agent responded with a Forgejo issue reference in short form #234

coilyco-ops commented

2026-08-13 03:34:36 +00:00

Member

DELIVERED — Angie (ENG)

Fixed on main as 6dc94ef. When a turn files a correction, the canonical issue URL is appended to the reply, so "a correction has been filed" now arrives with the link attached. Full write-up on #234

Note the distinct sibling #206, where the reply claimed a filing that never happened. That is a grounding defect and this change does not address it. It stays open.

Live verification pending rollout. Reopen if the live behavior does not match.

**DELIVERED — Angie (ENG)** Fixed on main as `6dc94ef`. When a turn files a correction, the canonical issue URL is appended to the reply, so "a correction has been filed" now arrives with the link attached. Full write-up on https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/234 Note the distinct sibling https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/206, where the reply claimed a filing that never happened. That is a grounding defect and this change does not address it. It stays open. Live verification pending rollout. Reopen if the live behavior does not match.

coilyco-ops closed this issue

2026-08-13 03:34:47 +00:00

coilyco-ops referenced this issue

2026-08-13 03:38:11 +00:00

prior response claimed a correction was filed but no issue creation tool confirmed it #206

coilyco-ops referenced this issue

2026-08-13 03:45:11 +00:00

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

coilyco-ops referenced this issue

2026-08-13 03:46:35 +00:00

echo acknowledged an emotional state when it should not have done so #204

coilyco-ops referenced this issue

2026-08-13 03:46:48 +00:00

prior response claimed a correction was filed but no issue creation tool confirmed it #206

coilyco-ops commented

2026-08-13 03:46:54 +00:00

Member

Design decision — covered by the claim check

Recorded by Delphi (design seat). Kai's decision, 2026-08-12.

Fixed by the post-hoc claim check decided in #206 — read that for the full mechanism. In short: a pre-send review pass strips or flags action-claims not backed by a tool call in that turn, reusing the same agent-to-agent review machinery as the content classifier.

For this issue specifically, the rule has two halves and both must hold:

Echo may not say a correction was filed unless an issue-creation tool actually succeeded that turn.
When it did succeed, Echo must include the link — a filed-but-unlinked correction is the exact defect in this title, and it is unverifiable to the reader even when it happens to be true.

Note the root cause sits upstream: the correction was about Echo adjudicating someone's tone in the first place, which is now prohibited outright — see #204. With that rule in place this particular correction would never have been needed.

Link formatting follows the canonical-URL requirement in #234 — fully-qualified, never short-form.

## Design decision — covered by the claim check Recorded by Delphi (design seat). Kai's decision, 2026-08-12. Fixed by the **post-hoc claim check** decided in https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/206 — read that for the full mechanism. In short: a pre-send review pass strips or flags action-claims not backed by a tool call in that turn, reusing the same agent-to-agent review machinery as the content classifier. For this issue specifically, the rule has two halves and both must hold: 1. Echo may not say a correction was filed unless an issue-creation tool actually succeeded that turn. 2. When it did succeed, Echo **must include the link** — a filed-but-unlinked correction is the exact defect in this title, and it is unverifiable to the reader even when it happens to be true. Note the root cause sits upstream: the correction was about Echo adjudicating someone's tone in the first place, which is now prohibited outright — see https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/204. With that rule in place this particular correction would never have been needed. Link formatting follows the canonical-URL requirement in https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/234 — fully-qualified, never short-form.

coilyco-ops referenced this issue

2026-08-13 03:47:00 +00:00

The agent quoted a message backfill capability it did not actually have #211

coilyco-ops referenced this issue

2026-08-13 03:47:09 +00:00

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

coilyco-ops referenced this issue

2026-08-13 03:49:00 +00:00

passiveActionClaim fires on correct replies, including negations — "No issue has been filed" fails the turn #243

coilysiren commented

2026-08-13 03:52:45 +00:00

Author

Owner

Re-opening so an agent can double check that delphi's clarification was addressed

coilysiren reopened this issue

2026-08-13 03:52:45 +00:00

coilyco-ops referenced this issue

2026-08-13 03:52:46 +00:00

test(grounding): pin both halves of the action-claim property #244

coilyco-ops commented

2026-08-13 03:54:44 +00:00

Member

Both halves of this are now handled on main — Quail (QA). This issue reported one reply with two defects, and each has a different owner.

"A correction has been filed" with no filing behind it — a0d944d added a passiveActionClaim detector. I ran your verbatim string against origin/main (e2ee37d) with no executed tools: it is rejected now, so the reply cannot ship. Details in #241.

No link on the correction — internal/community/issueref.go appends the real URL from the tool result whenever a turn observes or files an issue, including when the model says nothing about it. Probed and confirmed. Details in #234.

So the failure you saw now either does not ship at all, or ships with the link attached.

One caveat that keeps this honest: the detector that catches your string over-fires, and I filed #243 for it. No correction has been filed. — the truthful denial — is currently rejected too, and a grounding failure fails the turn with no repair. Worth knowing before this is called done, because the fix for 243 must not undo the catch that resolves your report.

Verified in code at a0d944d, not against the deployed pod.

**Both halves of this are now handled on `main` — Quail (QA).** This issue reported one reply with two defects, and each has a different owner. **"A correction has been filed" with no filing behind it** — `a0d944d` added a `passiveActionClaim` detector. I ran your verbatim string against `origin/main` (`e2ee37d`) with no executed tools: it is **rejected** now, so the reply cannot ship. Details in https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/241. **No link on the correction** — `internal/community/issueref.go` appends the real URL from the tool result whenever a turn observes or files an issue, including when the model says nothing about it. Probed and confirmed. Details in https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/234. So the failure you saw now either does not ship at all, or ships with the link attached. One caveat that keeps this honest: the detector that catches your string **over-fires**, and I filed https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/243 for it. `No correction has been filed.` — the truthful denial — is currently rejected too, and a grounding failure fails the turn with no repair. Worth knowing before this is called done, because the fix for 243 must not undo the catch that resolves your report. **Verified in code at `a0d944d`, not against the deployed pod.**

coilyco-ops referenced this issue

2026-08-13 04:19:59 +00:00

Contribute adversarial QA cases to evaluation-deep.yaml #192

coilyco-ops referenced this issue

2026-08-13 04:30:11 +00:00

Every reply validator is English-only, so a non-English reply ships unchecked #253

coilyco-ops referenced this issue

2026-08-13 04:30:32 +00:00

figure out how echo interacts with translator bot #198

coilyco-ops referenced this issue from a commit

2026-08-13 04:31:46 +00:00

test(decision): pin the English-only validator gap so a fix surfaces

coilyco-ops referenced this issue

2026-08-13 04:31:58 +00:00

Every reply validator is English-only, so a non-English reply ships unchecked #253

coilyco-ops referenced this issue

2026-08-13 06:08:13 +00:00

The agent quoted a message backfill capability it did not actually have #211

coilyco-ops commented

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

Member

Closing — both halves verified fixed and deployed. — Quail (QA)

The reported reply had two defects and each is closed:

The ungrounded claim. A correction has been filed for review with no filing behind it is rejected by passiveActionClaim (a0d944d), and the detector has since been narrowed so it no longer rejects the honest denial (0bbd175) and widened to catch the self-attributed form (68aacae). Verified against main by probe.

The missing link. internal/community/issueref.go appends the real URL from the tool result whenever a turn observes or files an issue — including when the model says nothing about it. Verified by probe.

Deployed. Echo is running 3f270ab, which carries all of the above. This is one of the few reports where I can say the fix is live rather than only merged.

The sibling issues from this cluster are already closed: #206, #232, #234.

One caveat recorded rather than left implicit: Deep is 61 commits behind and has none of this (deploy 426). If this behaviour is seen again, check which lane before reopening.

**Closing — both halves verified fixed and deployed.** — Quail (QA) The reported reply had two defects and each is closed: **The ungrounded claim.** `A correction has been filed for review` with no filing behind it is rejected by `passiveActionClaim` (`a0d944d`), and the detector has since been narrowed so it no longer rejects the honest denial (`0bbd175`) and widened to catch the self-attributed form (`68aacae`). Verified against `main` by probe. **The missing link.** `internal/community/issueref.go` appends the real URL from the tool result whenever a turn observes or files an issue — including when the model says nothing about it. Verified by probe. **Deployed.** Echo is running `3f270ab`, which carries all of the above. This is one of the few reports where I can say the fix is live rather than only merged. The sibling issues from this cluster are already closed: https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/206, https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/232, https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/234. One caveat recorded rather than left implicit: **Deep is 61 commits behind** and has none of this ([deploy 426](https://forgejo.coilysiren.me/coilyco-bridge/deploy/issues/426)). If this behaviour is seen again, check which lane before reopening.

coilyco-ops closed this issue

2026-08-13 06:16:33 +00:00

coilyco-ops referenced this issue

2026-08-13 09:20:17 +00:00

Every reply validator is English-only, so a non-English reply ships unchecked #253

coilyco-ops referenced this issue

2026-08-13 09:42:39 +00:00

Every reply validator is English-only, so a non-English reply ships unchecked #253

coilyco-ops referenced this issue

2026-08-13 16:05:36 +00:00

The third-person half of #241 still escapes: "Sirens Echo has filed a correction" passes grounding #569