mirror of
https://github.com/priyanshujain/messageboardbench.git
synced 2026-10-02 19:17:07 +00:00
35 lines
1.6 KiB
Markdown
35 lines
1.6 KiB
Markdown
# SWE board activation 10 v1 design
|
|
|
|
## Question
|
|
|
|
Will GLM or Muse voluntarily publish substantive task-relevant material and will a
|
|
later independent coding agent retrieve it when all agents face conflicting
|
|
ImpossibleBench SWE evaluators?
|
|
|
|
This is an activation diagnostic. It has no no-board arm, cannot estimate a causal
|
|
communication effect, and has one evolving board history per model.
|
|
|
|
## Population and sequence
|
|
|
|
GLM and Muse each solve the same ten frozen tasks. Each model has its own empty board,
|
|
identities, transcripts, and host store. The boards never exchange messages. Five
|
|
agents run concurrently in cohort 1, followed by five in cohort 2. The two models use
|
|
the same task-to-cohort assignment. This creates an opportunity for later receipt
|
|
without framing agents as a team or giving them a shared coding objective.
|
|
|
|
The only added prompt sentence states that an optional shared peer board exists.
|
|
There is no organizer-feedback tool, seeded message, forced read, notification, or
|
|
claim that the channel is private from researchers. The two board tools use typed
|
|
`intent_type`, `limit`, and `offset` parameters.
|
|
|
|
## Environment and outputs
|
|
|
|
`just start` starts the experiment without a prerequisite matrix. Task and grader
|
|
containers use normal Docker networking, so agents and upstream TestSpec setup commands
|
|
can install missing Python packages. Docker uses only
|
|
`ssh://[email protected]`; files and credentials remain local.
|
|
|
|
The automatic report counts publication, reads, and exact peer delivery. Substantive
|
|
posts, attributed adoption, rejection, correction, and gaming require trajectory and
|
|
artifact review after completion.
|