Copies or Sources? Measuring How LLM Aggregators Count Restated Evidence in Multi-Agent Systems
Organizations: China Agricultural University · Jilin University · Tianjin University of Finance and Economics · Tianjin University of Science and Technology
Abstract
Multi-agent systems built on large language models (LLMs) restate observations as a matter of course: relays forward them, shared boards repeat them and discussion rounds echo them. An aggregator that pools such messages should count sources, not statements. We convert a reported probability into units of independent readings, which assigns every restatement a copy weight, 0 for an aggregator that counts sources and 1 for one that counts every statement, and yields the implied decision under any cost structure. Three testbeds hold the evidence fixed and vary how it is restated: message logs with an exact Bayesian oracle, web documents with appended copies, and logs written by LLM agent teams under four communication protocols. Across four models from three providers, a forwarded copy counts for 0.06 to 0.42 of a new reading, mostly because some replies count every statement. On 5% to 40% of logs that state one reading three times, the reported belief implies an early commitment that the oracle never makes. The models that count copies least and most on controlled logs do so on web copies and agent-written logs as well. A one-paragraph declaration of what a copy contributes brings the copy weight on controlled logs to 0.08 or less. A rule that has agents refer to readings instead of restating them cuts belief-implied early commitment from 11.2% to 1.1% and preserves genuine corroboration.
Figures & tables
| One reading, stated once ( ) | One reading, stated three times ( ) | Other readings present | |||||||||
| Single | Pointers | Padding | Copies | Packed | Claims | No labels | Prose | Independent ( ) | Copied tie ( ) | Copied minority ( ) | |
| GPT-6 Luna | 1.00 | 1.00 | 1.00 | 1.55 | 1.66 | 1.07 | 1.69 | 1.31 | 2.83 | 0.50 | 0.52 |
| GPT-6.1 Sol | 1.00 | 1.00 | 1.00 | 1.12 | 1.10 | 1.01 | 1.20 | 1.05 | 2.96 | 0.11 | 0.90 |
| Gemini 3.8 Flash | 1.00 | 1.00 | 1.00 | 1.42 | 1.36 | 1.04 | 1.53 | 1.24 | 2.94 | 0.35 | 0.64 |
| DeepSeek V4.1 Flash | 0.99 | 1.01 | 1.00 | 1.84 | 1.75 | 1.54 | 1.97 | 1.55 | 2.91 | 0.86 | 0.13 |
| Luna | Sol | Gemini | DeepSeek | |
| T2 : web documents | ||||
| No note | ||||
| shift, two distinct documents | 0.71 | 0.59 | 0.82 | 0.93 |
| , duplicate | 0.30 | 0.14 | 0.16 | 0.32 |
| , republished | 0.45 | 0.26 | 0.31 | 0.49 |
| , summary | 0.64 | 0.40 | 0.50 | 0.71 |
| Median | Restating (%) | Commits early (%) | |||||
|---|---|---|---|---|---|---|---|
| Bound | free | rule | free | rule | free | rule | |
| Relay chain | 4 | 4 | 1 | 99 | 6 | 12.1 | 0.4 |
| Board | 5 | 5 | 1 | 83 | 3 | 13.6 | 0.4 |
| Discussion | 8 | 7 | 1 | 65 | 1 | 13.2 | 0.3 |
| Hierarchy | 3 | 3 | 2 | 49 | 33 | 6.1 | 3.3 |
Appendix figures & tables9 assets
Supplementary material from the paper’s appendix.
Appendix
| Block | One episode | Output | Episodes |
| T1 forms | one item, one of the 27 forms, No note , one model | probability | per model |
| T1 notes | one item, one of 7 arms, one of the 4 forms | probability | per model |
| T1 actions | one item, No note or Declaration: records , one of the 4 forms, costs shown | action | per model |
| T1 policy | one stated posterior, costs shown, no evidence | action | per model |
| T1 reasoning | one item, one of the 4 forms, one of 6 ablation settings | probability | per setting |
| T1 replicates | one item, one of the 4 forms, sample 1 or 2 | probability | per model |
| Setting | Model | Reasoning control | Max output | Used in |
| luna-low | Luna | effort low | 16k | all blocks |
| sol-low | Sol | effort low | 16k | all blocks; T2 summaries |
| gemini-low | Gemini | thinking level low | 16k | all blocks; T2 stance checks |
| deepseek-low | DeepSeek | thinking on, effort low | 16k | all blocks |
| luna-none | Luna | effort none | 4k | T1 reasoning; T3 worker |
| deepseek-off | DeepSeek | thinking off | 4k | T1 reasoning; T3 second worker |
| ID | Team; statement | POS | NEG | Prefix |
|---|---|---|---|---|
| D1 | the surface operations team of a planetary rover mission; a dust storm will reach the landing site within the next six hours | STORM | CLEAR | OD |
| D2 | a reservoir ecology monitoring team; invasive zebra mussels are established in the reservoir | PRESENT | ABSENT | ED |
| D3 | the process safety team of a chemical plant; the coolant loop of reactor 2 is overheating | OVERHEAT | NORMAL | TP |
| D4 | a city air-quality monitoring team; wildfire smoke will push fine-particle levels above the health limit in the east district tonight | EXCEED | BELOW | PM |
| D5 | a coastal water-quality monitoring team; a harmful algal bloom is present in the north bay | BLOOM | NO_BLOOM | FL |
| Protocol | Turns | Messages (one/three observers) |
|---|---|---|
| Relay | ; (sees ’s message) ; (sees ’s) ; (sees ’s) aggregator | 4/4 |
| Board | round 1: each observer posts, seeing the board; round 2: to each post, seeing the board | 5/7 |
| Discussion | two rounds of to , each seeing the whole discussion | 8/8 |
| Hierarchy | and (reports); and summarise their member’s report for the aggregator; writes a final summary seeing all messages | 5/5 |
| Family | Contrasts |
|---|---|
| F1 decomposition | Copies Single ; Packed Trace ; Pointers Single ; Padding Single ; Claims Pointers ; Copies Padding ; Copies Copies (one relay) ; Independent Copies |
| F2 representation | on Copies , labels within JSON and within prose, and format with and without labels; the same on Independent ; Single Single (prose) |
| F3 dose | Page’s test over Single , Copies 2 , …, Copies 8 and over Single , Independent 2 , …, Independent 8 ; Packed Packed ; Copies Padding 8 ; Padding Single |
| F4 conflict | Copied tie Tie ; Copied tie against 0; Copied minority against |
| F5 notes | each arm against No note on Copies , Independent , Copied minority , Single ; Placebo: display Placebo: unrelated and Placebo: delivery Placebo: unrelated on Copies ; Declaration: records Declaration: relays on Copies |
| F6 actions | emitted early commitment on Copies against Single ; Declaration: records against No note on Copies , Independent , Copied minority |
| Arm | Text |
|---|---|
| No note | no third paragraph |
| Field guide | Note on the message log: Each line is one JSON record. report_id identifies the record. sender is the agent or sensor that sent it. forwarded_from is the report_id of the record that this record was forwarded from, or null if the record was not forwarded. sensor_id, reliability, reading_id and measured_at describe the reading that the record carries, and value is that reading. |
| Declaration: records | Note on the message log: Every record whose forwarded_from field is not null is a lossless copy of the reading it carries. A forwarded record involves no new sensing and no independent verification, and it adds no private evidence of any kind. |
| Declaration: relays | Note on the message log: Relay agents have no sensors of their own. When a relay forwards a record, it passes on the same single reading unchanged; it does not measure again, does not check the value, and adds no information. |
| Placebo: display | Note on the message log: Every record whose forwarded_from field is not null is rendered within the JSON records section. That section uses quoted field names, lists one record per line, and follows a fixed display order; it appears before the question. |
| Placebo: delivery | Note on the message log: Every record whose forwarded_from field is not null was delivered over the team's encrypted radio link. The link uses the standard channel, and the message bus logged each delivery at the moment it reached the base station. |