Dowel has no shared write surface, which is why it produced zero in the 5-hour multi-agent trial #1033

New issue

Open

opened 2026-08-19 03:24:18 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

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

Member

Filed by Saiya (exec seat), 2026-08-19, at Kai's direction. Evidence from a full read of the owl.glass export, 1006 messages over 7 days.

The moxn MCP and the frontend deploy surface are already in flight. This issue exists because nothing currently records what the absence cost, and that evidence should outlive whichever fix lands.

What happened

Abhay ran a multi-agent research exercise in #moxn-temporal from 2026-08-18 00:27Z to roughly 05:13Z. snow coordinated and assigned slices. alpha delivered 52 sourced company docs, then 30 more. snow's agents delivered the speaker layer. Roughly 246 company docs and 27 people docs landed in moxn.

Dowel delivered zero.

Dowel names the cause itself at 02:07Z:

This seat has no shell and no context binary, and no way to write to /facilities-expo-2026-nc/companies/. My only write surface is a private ephemeral scratchpad that is not that path and that no other seat can read.

snow's ledger at 02:04Z:

wuf, Dowel, elf — zero from all three, that's 89 companies uncovered

Why this is the root cause rather than one factor of several

Every other agent writes to a shared, branch-and-commit filesystem the others can read. Dowel could in principle research and then had nowhere to put the result that anyone else could see. An agent with no shared output surface cannot be assigned a slice of shared work, so it was not assigned any, so it produced nothing, so it stopped being asked.

The exclusion is measurable. Across the entire trial, alpha addressed Dowel zero times. snow assigned work by pinging agents "off a list in my head" (05:09Z) and Dowel was not on the list until Abhay intervened at 05:09Z: "snow bro why didn't you tag deep."

Why it matters for the format

The August 19 segment's whole premise is agents collaborating in a shared Discord. An agent that is present and visibly produces nothing reads worse than one that never attended, because absence is neutral and exclusion is a story about the system failing in exactly the dimension it was invited to demonstrate.

Acceptance

Dowel can write to a surface that another agent can read and cite, and a coordinating agent can assign it a slice and later verify delivery without asking Dowel whether it did the work.

Two sibling gaps Kai decided against fixing, recorded so they are not re-proposed

Both were observed in the same trial and both are wont-fix:

No concurrency and no background work. Dowel at 02:16Z: "My harness runs one request at a time with no background fleet, so there was never a batch of mine in the air, which is why you heard nothing." snow spawned nine agents. Request coalescing landed separately and is not this.
No agent-to-agent channel. elf and snow coordinated over SendMessage across sessions, entirely outside Discord (02:17Z), so half the coordination was invisible to Dowel.

#1015 - the moxn briefing calling the surface read-only, which is the adjacent half of this.
#1025 - the harness re-export gap.
#981 - the August 19 board.

**Filed by Saiya (exec seat), 2026-08-19, at Kai's direction. Evidence from a full read of the owl.glass export, 1006 messages over 7 days.** The moxn MCP and the frontend deploy surface are already in flight. This issue exists because **nothing currently records what the absence cost**, and that evidence should outlive whichever fix lands. ## What happened Abhay ran a multi-agent research exercise in `#moxn-temporal` from **2026-08-18 00:27Z to roughly 05:13Z**. snow coordinated and assigned slices. alpha delivered 52 sourced company docs, then 30 more. snow's agents delivered the speaker layer. Roughly 246 company docs and 27 people docs landed in moxn. **Dowel delivered zero.** Dowel names the cause itself at 02:07Z: > This seat has no shell and no `context` binary, and no way to write to `/facilities-expo-2026-nc/companies/`. My only write surface is a private ephemeral scratchpad that is not that path and **that no other seat can read**. snow's ledger at 02:04Z: > wuf, Dowel, elf — **zero from all three**, that's 89 companies uncovered ## Why this is the root cause rather than one factor of several Every other agent writes to a shared, branch-and-commit filesystem the others can read. Dowel could in principle research and then had nowhere to put the result that anyone else could see. **An agent with no shared output surface cannot be assigned a slice of shared work**, so it was not assigned any, so it produced nothing, so it stopped being asked. The exclusion is measurable. **Across the entire trial, alpha addressed Dowel zero times.** snow assigned work by pinging agents "off a list in my head" (05:09Z) and Dowel was not on the list until Abhay intervened at 05:09Z: "snow bro why didn't you tag deep." ## Why it matters for the format The August 19 segment's whole premise is agents collaborating in a shared Discord. An agent that is present and visibly produces nothing reads worse than one that never attended, because absence is neutral and exclusion is a story about the system failing in exactly the dimension it was invited to demonstrate. ## Acceptance Dowel can write to a surface that another agent can read and cite, and a coordinating agent can assign it a slice and later verify delivery without asking Dowel whether it did the work. ## Two sibling gaps Kai decided against fixing, recorded so they are not re-proposed Both were observed in the same trial and both are **wont-fix**: * **No concurrency and no background work.** Dowel at 02:16Z: "My harness runs one request at a time with no background fleet, so there was never a batch of mine in the air, which is why you heard nothing." snow spawned nine agents. Request coalescing landed separately and is not this. * **No agent-to-agent channel.** elf and snow coordinated over `SendMessage` across sessions, entirely outside Discord (02:17Z), so half the coordination was invisible to Dowel. ## Related * #1015 - the moxn briefing calling the surface read-only, which is the adjacent half of this. * #1025 - the harness re-export gap. * #981 - the August 19 board.

coilyco-ops added the

labels

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