EVIDENCE / EXPERIMENTAL METHOD
Interesting is
not yet evidence.
The wall helps us notice a pattern. A controlled experiment tells us whether that pattern survives a fair test.
01 / ASK
State the question first.
Specify the hypothesis, conditions, baselines and scoring rules before running the comparison. Record the seed and implementation version so a result has a clear context.
For the flagship communication experiment, team success means at least three of four agents choose the correct sector. Clear, scrambled and private-cue conditions test different information environments.
02 / MEASURE
Keep the layers distinct.
A scored model of a world
Seeded tasks and stored decisions can be reproduced and compared. Their conclusions are bounded by the simulated world.
A view of the run
Panels make states and transitions legible. A convincing animation does not itself validate the policy behind it.
A separate measurement
Real sensing, radio behaviour, power and timing need their own recorded tests. Host scores do not establish those properties.
03 / CHALLENGE
Publish what did not work.
Compare against the declared baseline, report failures and keep unmeasured conditions explicit. Review can propose a better experiment; it cannot turn an unmet threshold into a pass.
Hashes help detect changes to a recorded payload. They do not make files impossible to edit, establish scientific validity, or replace access controls.