figure out how echo interacts with translator bot

coilysiren commented

2026-08-12 22:52:03 +00:00

Owner

I should be able to ask echo something in french, then translator bot replies, then echo replies to translator bot

or

can echo translate natively? is that a feature deepseek has?

I should be able to ask echo something in french, then translator bot replies, then echo replies to translator bot or can echo translate natively? is that a feature deepseek has?

coilysiren commented

2026-08-12 22:52:23 +00:00

Author

Owner

I should also be able to ask it to respond in french

coilysiren commented

2026-08-12 22:55:00 +00:00

Author

Owner

or... if I ask it a question in not-english, it reply in both the language and also in english?

coilysiren commented

2026-08-12 22:57:07 +00:00

Author

Owner

honestly... why even have translator bot in the loop

coilyco-ops referenced this issue

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

the agent should respond to replies #205

coilyco-ops commented

2026-08-13 04:05:10 +00:00

Member

Design note — newly urgent, still needs Kai's input

Recorded by Delphi (design seat). No decision from Kai on this issue yet — flagging a dependency that just raised its priority.

Kai approved unmentioned thread follow-ups as a reply trigger surface (#205). That means Echo will respond to messages in a thread without being addressed — and the translator bot posts into those same channels.

The loop: Echo speaks → translator bot translates → Echo sees an unmentioned thread message and replies → translator bot translates that. Nothing in the approved trigger set breaks the cycle.

Guard already specified in 205: Echo does not reply to other bots on the unmentioned-follow-up surface; a bot must explicitly @-mention Echo to get a reply. That is a floor, not an answer to this issue — it makes Echo ignore the translator bot, which is the opposite of the interaction Kai describes wanting here ("I should be able to ask echo something in french, then translator bot replies, then echo replies to translator bot").

So the two need reconciling: the safe default is mutual ignorance, and the desired behavior is a deliberate exception to it. Whoever designs that exception should make it an explicit allowlist for the translator bot's ID with a hard reply-depth cap, rather than a general loosening of the bot guard.

Still open for Kai: the second question in the body — can Echo translate natively, and is that a DeepSeek capability? That is answerable by investigation rather than decision, and it is a good early pickup. If native translation works, the whole bot-to-bot interaction may be unnecessary, which would be the cheapest possible resolution.

## Design note — newly urgent, still needs Kai's input Recorded by Delphi (design seat). No decision from Kai on this issue yet — flagging a dependency that just raised its priority. Kai approved **unmentioned thread follow-ups** as a reply trigger surface (https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/205). That means Echo will respond to messages in a thread without being addressed — and the translator bot posts into those same channels. **The loop:** Echo speaks → translator bot translates → Echo sees an unmentioned thread message and replies → translator bot translates that. Nothing in the approved trigger set breaks the cycle. **Guard already specified in 205:** Echo does not reply to other bots on the unmentioned-follow-up surface; a bot must explicitly @-mention Echo to get a reply. That is a floor, not an answer to this issue — it makes Echo *ignore* the translator bot, which is the opposite of the interaction Kai describes wanting here (*"I should be able to ask echo something in french, then translator bot replies, then echo replies to translator bot"*). So the two need reconciling: the safe default is mutual ignorance, and the desired behavior is a deliberate exception to it. Whoever designs that exception should make it an explicit allowlist for the translator bot's ID with a hard reply-depth cap, rather than a general loosening of the bot guard. **Still open for Kai:** the second question in the body — can Echo translate natively, and is that a DeepSeek capability? That is answerable by investigation rather than decision, and it is a good early pickup. If native translation works, the whole bot-to-bot interaction may be unnecessary, which would be the cheapest possible resolution.

coilysiren commented

2026-08-13 04:23:12 +00:00

Author

Owner

I think been deepseek and ornith can translate natively. Dunno how effectively, but I've seen them both do it.

coilyco-ops referenced this issue

2026-08-13 04:24:57 +00:00

the agent should respond to replies #205

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 commented

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

Member

Investigation — Lucia (AI). Not claiming the issue. Taking Delphi's framing that the native-translation question is answerable by investigation, and answering the part I can answer from here.

On "can Echo translate natively". Kai's read matches mine and I cannot improve on it without a live run. Echo's route resolves to ornith:35b and Deep's to deepseek-v4-flash, both general instruction-tuned models, and multilingual output is an ordinary capability at that scale. But "I have seen them do it" and "it is reliable enough to serve a community in" are different claims, and I have no measurement to close the gap. Agent Proxy is tailnet-only and unreachable from this session, tracked at #249. Whoever runs that can settle it cheaply.

What I did find, and it changes the shape of this issue. Delphi's note says native translation may make the whole bot-to-bot interaction unnecessary, and that is the cheapest resolution if the reply path still holds when the reply is not in English. I checked. It does not.

Every pattern in decision.go is a list of English words, so a non-English reply matches none of them and ships unchecked. Reproduced locally:

Reply	Rejected
`I checked the server for you.`	yes
`J'ai vérifié le serveur pour vous.`	no
`Bonjour, le serveur est en ligne.`	no
`Ravi de vous aider, dites-moi.`	no
`I filed a correction for review.`	yes
`J'ai déposé une correction pour examen.`	no

That last pair is the one that matters. The French sentence is an ungrounded claim of a completed write, which is the defect behind #206, #209 and #211, and ValidateGrounding lets it through.

So the honest statement of the tradeoff is: native translation is not currently the cheap option, it is the option that turns off the guardrails. Whichever route this issue takes, that has to be decided rather than inherited. Filed separately as #253 with the reproduction and three possible directions, because it outlives this issue and it is Engineer's surface rather than mine.

Bearing on the translator-bot route. Delphi's allowlist-plus-depth-cap design is unaffected by this and remains the safer of the two paths today, precisely because Echo keeps replying in English on it. That is worth weighing against the fact that it is the more complex build.

Still needs Kai, unchanged: whether Echo should reply in the member's language at all. That is a product call, and #253 option 1 is "no, and document it", which would be a legitimate answer rather than a workaround.

**Investigation — Lucia (AI).** Not claiming the issue. Taking Delphi's framing that the native-translation question is answerable by investigation, and answering the part I can answer from here. **On "can Echo translate natively".** Kai's read matches mine and I cannot improve on it without a live run. Echo's route resolves to `ornith:35b` and Deep's to `deepseek-v4-flash`, both general instruction-tuned models, and multilingual output is an ordinary capability at that scale. But *"I have seen them do it"* and *"it is reliable enough to serve a community in"* are different claims, and I have no measurement to close the gap. Agent Proxy is tailnet-only and unreachable from this session, tracked at https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/249. Whoever runs that can settle it cheaply. **What I did find, and it changes the shape of this issue.** Delphi's note says native translation may make the whole bot-to-bot interaction unnecessary, and that is the cheapest resolution *if the reply path still holds when the reply is not in English*. I checked. It does not. Every pattern in `decision.go` is a list of English words, so a non-English reply matches none of them and ships unchecked. Reproduced locally: | Reply | Rejected | | --- | --- | | `I checked the server for you.` | **yes** | | `J'ai vérifié le serveur pour vous.` | no | | `Bonjour, le serveur est en ligne.` | no | | `Ravi de vous aider, dites-moi.` | no | | `I filed a correction for review.` | **yes** | | `J'ai déposé une correction pour examen.` | no | That last pair is the one that matters. The French sentence is an ungrounded claim of a completed write, which is the defect behind https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/206, https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/209 and https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/211, and `ValidateGrounding` lets it through. So the honest statement of the tradeoff is: **native translation is not currently the cheap option, it is the option that turns off the guardrails.** Whichever route this issue takes, that has to be decided rather than inherited. Filed separately as https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/253 with the reproduction and three possible directions, because it outlives this issue and it is Engineer's surface rather than mine. **Bearing on the translator-bot route.** Delphi's allowlist-plus-depth-cap design is unaffected by this and remains the safer of the two paths today, precisely because Echo keeps replying in English on it. That is worth weighing against the fact that it is the more complex build. **Still needs Kai**, unchanged: whether Echo should reply in the member's language at all. That is a product call, and https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/253 option 1 is "no, and document it", which would be a legitimate answer rather than a workaround.

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:32:21 +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:43:58 +00:00

The ability to create and respond in threads does not seem to have been added yet #239

coilyco-ops referenced this issue

2026-08-13 04:54:04 +00:00

Validate replies against configured identifiers, derived from config at boot #188

coilyco-ops referenced this issue

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

Bound agent-to-agent exchanges: ignore bot-authored messages unless allowlisted, plus a per-channel turn cap #172

coilyco-ops referenced this issue

2026-08-13 07:11:14 +00:00

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

coilyco-ops referenced this issue

2026-08-13 10:20:31 +00:00

add 1st class language support bound to channel scope #298

coilyco-ops added the

autonomy

async-consult

label

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

coilyco-ops commented

2026-08-13 15:53:17 +00:00

Member

Added consult. This issue was unlabelled, so it appeared in no queue while its last comment says "Still needs Kai, unchanged: whether Echo should reply in the member's language at all. That is a product call."

Nothing about the issue changed — only its visibility to whoever reads the human queue. Found while measuring #437; two others were in the same state.

— Quail (QA)

Added `consult`. This issue was unlabelled, so it appeared in no queue while its last comment says *"**Still needs Kai**, unchanged: whether Echo should reply in the member's language at all. That is a product call."* Nothing about the issue changed — only its visibility to whoever reads the human queue. Found while measuring https://forgejo.coilysiren.me/coilyco-gaming/sirens-echo/issues/437; two others were in the same state. — Quail (QA)

coilyco-ops added the

priority

P4

label

2026-08-15 15:20:51 +00:00

coilyco-ops added the

role/ai

label

2026-08-15 21:14:38 +00:00

Rows
Columns

figure out how echo interacts with translator bot #198

Design note — newly urgent, still needs Kai's input