executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
aamas-reproducibilityUse when strengthening AAMAS reproducibility evidence for interaction claims, including proofs and game definitions, opponent and population sets, self-play protocols, random seeds, compute, uncertainty on strategic outcomes, baselines, and consistency between what the paper claims about agents and what the artifact can actually show.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this before submission and again before camera-ready. The reproducibility question at AAMAS is not only "can I rerun the model" but "can I reproduce the interaction - the same agents, the same game, the same emergent outcome."
| Claim | Pure-theory answer | Learning-plus-game answer |
|---|---|---|
| Solution concept reached | Proof with the game and information structure stated | Plus convergence curves under other agents' adaptation |
| Opponents / population | NA if fully analytical | The exact opponent set and how it was chosen |
| Seeds and variance | NA for deterministic results | Required for every stochastic curve and payoff table |
| Compute | NA | Hardware, per-run time, and total number of self-play runs |
Claiming an equilibrium result while the evaluation only shows two fixed agents playing once is the recognizable AAMAS gap: reviewers read the mismatch between the strategic claim and the thinness of the interaction evidence as carelessness about the rest.
Consider a submission proving convergence to a coarse-correlated equilibrium in a repeated game, validated by self-play. Its reproducibility spine: the game generator and payoff scale, the learning rule and its step sizes, the opponent set, the replication seeds, the convergence metric, and one honest sentence on the regime where convergence is only empirical, not proved.
For AAMAS, the strategic core should be turnkey because reviewers actually re-run small games; large real-world or human-in-the-loop pipelines may stay scripted with deviations documented. Stating the achieved level honestly beats overpromising turnkey behavior that fails on a clean machine.
[Claim inventory] <claim -> evidence location>
[Artifact consistency] complete / inconsistent / missing
[Interaction reproducibility gaps] <game/opponents/seeds/uncertainty/compute>
[Paper fixes] <must appear in main PDF>
[Supplement fixes] <appendix or artifact additions>