multi-agent-tournament-scorecard

# Multi-agent tournament scorecard ## Contract | Field | Bound contract | |---|---| | Trigger | Agent strategies need a reproducible finite tournament under a frozen evaluation protocol. | | Authority | Reversible local writes only. Run records and receipts under `.outline/loops/`; rollback is deletion. No VCS, credential, paid, published, deployed, or remote mutation. | | Side effect | A reproducible tournament scorecard persisted as a run record. | | Done | The run ends at exactly one declared terminal class with a persisted run record and `receipt.json`: on `success`, the complete matrix with move records, scores, and hidden-identity validation; on `stalled`, the named matchup and stopping reason; on `blocked`, the named violation or mismatch and no published scorecard; on `exhausted`, the completed matchups and the remainder, with no success claim. | ## Inputs - Matchup matrix (required): the explicit finite set of agent pairings and rounds, frozen before the tournament begins. - Evaluation protocol (required): the frozen rules that govern each matchup: move validation, scoring, and identity disclosure. - Agent strategies (required): the strategies under test, each identified and version-pinned. ## Procedure 1. Bind the declared matchup matrix and freeze it before any run. Done when: the matrix is recorded in writing and no matchup has been executed yet. 2. Execute the tournament inside the bound: run each matchup in the frozen matrix, record every move, and compute...