Dowel posts fully empty messages into the channel #1035

New issue

Closed

opened 2026-08-19 03:24:43 +00:00 by coilyco-ops · 1 comment

coilyco-ops commented

2026-08-19 03:24:43 +00:00

Member

Filed by Saiya (exec seat), 2026-08-19, at Kai's direction. Evidence from the owl.glass export.

Kai's read: easy fix, at both the mcp-beaver layer and the harness layer.

The measurement, corrected

My first pass reported 23 empty Dowel messages. That was wrong and inflated. 18 of the 23 are THREAD_STARTER_MESSAGE, a Discord artifact that lives inside a thread rather than a visible post, and one is a member-join notice.

The real figure, counting only what a reader of #moxn-temporal sees:

45 main-channel messages from Dowel
34 substantive replies
7 thread-creation notices, tracked separately in the thread-naming issue
4 replies with no content at all

So roughly 9% of Dowel's visible posts are blank, not 26%. Smaller than first reported, still worth fixing, and the honest number is the one to work from.

Why it still matters at 4

A blank message from an agent in a shared channel with other people's agents does not read as a minor glitch. It reads as the thing being broken, and it costs the same attention as a real failure while carrying none of the information a real failure would.

It also compounds: on 11 of 32 occasions a human addressed Dowel directly, another agent answered first (alpha 7, snow 4), and several of those were cases where Dowel's contribution to the channel was an empty post.

Acceptance

A turn that has nothing to say posts nothing, or posts a deliberate one-token acknowledgement. No zero-content message reaches the channel from either layer. A repeat of the 08-18 window shows zero blank main-channel posts.

Scope

Both layers, per Kai. Fix where the reply is assembled in the harness, and at the mcp-beaver layer so a tool path cannot produce the same shape.

Operational improvement rather than a feature under the #929 amendment, since it changes only how well the lane does what it already does. Reachable before the stream.

**Filed by Saiya (exec seat), 2026-08-19, at Kai's direction. Evidence from the owl.glass export.** Kai's read: easy fix, at both the mcp-beaver layer and the harness layer. ## The measurement, corrected My first pass reported 23 empty Dowel messages. **That was wrong and inflated.** 18 of the 23 are `THREAD_STARTER_MESSAGE`, a Discord artifact that lives inside a thread rather than a visible post, and one is a member-join notice. The real figure, counting only what a reader of `#moxn-temporal` sees: * **45 main-channel messages from Dowel** * 34 substantive replies * 7 thread-creation notices, tracked separately in the thread-naming issue * **4 replies with no content at all** So roughly **9% of Dowel's visible posts are blank**, not 26%. Smaller than first reported, still worth fixing, and the honest number is the one to work from. ## Why it still matters at 4 A blank message from an agent in a shared channel with other people's agents does not read as a minor glitch. It reads as the thing being broken, and it costs the same attention as a real failure while carrying none of the information a real failure would. It also compounds: on **11 of 32 occasions a human addressed Dowel directly, another agent answered first** (alpha 7, snow 4), and several of those were cases where Dowel's contribution to the channel was an empty post. ## Acceptance A turn that has nothing to say posts nothing, or posts a deliberate one-token acknowledgement. No zero-content message reaches the channel from either layer. A repeat of the 08-18 window shows zero blank main-channel posts. ## Scope Both layers, per Kai. Fix where the reply is assembled in the harness, and at the mcp-beaver layer so a tool path cannot produce the same shape. Operational improvement rather than a feature under the #929 amendment, since it changes only how well the lane does what it already does. Reachable before the stream.

coilyco-ops added the

labels

2026-08-19 03:24:43 +00:00

coilyco-ops referenced this issue

2026-08-19 04:03:09 +00:00

Epic: August 19 Temporal Vibe Check demo readiness, the work that is on camera #981

coilyco-ops added this to the August 19 Temporal Vibe Check milestone

2026-08-19 04:12:50 +00:00

coilyco-ops commented

2026-08-19 05:16:31 +00:00

Author

Member

Picking this up now (AI Engineer seat, 2026-08-19 ~05:35Z), so another seat does not start it in parallel. Will comment here if I stop before landing it.

coilyco-ops modified the milestone from August 19 Temporal Vibe Check to August 19 morning of

2026-08-19 05:35:04 +00:00

coilyco-ops referenced this issue from a commit

2026-08-19 06:02:32 +00:00

fix(reply): a blank never reaches the channel, the message gets a mark instead

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

2026-08-19 06:02:53 +00:00

fix(reply): a blank never reaches the channel, the message gets a mark instead #1060