docs: Bench allows game_outcome from the round creator (#291)

OP OpenVibers committed 7 days ago · 10413f2b26 · 1 file, +1 −1

Bench's creator-vote guard is only on human_pairwise; the stale paragraph
claimed it blocked service-submitted game_outcome judgements and kept the
job off. The job can submit outcomes as the games principal.

Changes

ddiff --git a/docs/ai-matches.md b/docs/ai-matches.md
iindex 10ea18e..e3a5085 100644
---- a/docs/ai-matches.md
++++ b/docs/ai-matches.md
@@@ -23,4 +23,4 @@ Required Network service grants for principal `games`:
  
  Match records, moves, battle events, and Bench receipts are stored in `ai_matches`. A failed Bench submission leaves the local match with `failed` status for operator inspection; failed submissions are not automatically retried because Bench's create endpoints have no idempotency key for this workflow. Bench also applies its own round quotas (currently three rounds per creator per day by default); one match uses `GAMES_AI_MATCHES_GAMES + 1` Bench rounds including `games.fun`, so its quota must be raised for longer or multiple daily matches.
  
--Bench currently rejects a `game_outcome` judgement when its subject is also the round creator. This job creates rounds and casts outcomes with the same `games` service principal, so its first judgement receives `bench.creator_cannot_vote` and the local match is marked failed. Bench needs to permit service-submitted `game_outcome` judgements from the round creator, or provide a separate authorized judge identity, before enabling this job in production.
++Bench's creator-vote guard applies only to `human_pairwise`, where a person must not judge a round they started. A `game_outcome` judgement from the `games` service principal that also created the round is allowed (`server/store.js`, `castJudgement`), so this job can submit its outcomes in production without a separate judge identity.

diff --git a/docs/ai-matches.md b/docs/ai-matches.md

index 10ea18e..e3a5085 100644

--- a/docs/ai-matches.md

+++ b/docs/ai-matches.md

@@ -23,4 +23,4 @@ Required Network service grants for principal `games`:

Match records, moves, battle events, and Bench receipts are stored in `ai_matches`. A failed Bench submission leaves the local match with `failed` status for operator inspection; failed submissions are not automatically retried because Bench's create endpoints have no idempotency key for this workflow. Bench also applies its own round quotas (currently three rounds per creator per day by default); one match uses `GAMES_AI_MATCHES_GAMES + 1` Bench rounds including `games.fun`, so its quota must be raised for longer or multiple daily matches.

-Bench currently rejects a `game_outcome` judgement when its subject is also the round creator. This job creates rounds and casts outcomes with the same `games` service principal, so its first judgement receives `bench.creator_cannot_vote` and the local match is marked failed. Bench needs to permit service-submitted `game_outcome` judgements from the round creator, or provide a separate authorized judge identity, before enabling this job in production.

+Bench's creator-vote guard applies only to `human_pairwise`, where a person must not judge a round they started. A `game_outcome` judgement from the `games` service principal that also created the round is allowed (`server/store.js`, `castJudgement`), so this job can submit its outcomes in production without a separate judge identity.