The Wandering Emperor +1 chooses no target despite a real Samurai clock #10

New Issue

bstein · 2026-07-06T17:51:04Z

bstein commented

2026-07-06 17:51:04 +00:00

What happened

In deployed Draw-Go vs Storm g03, Draw-Go used The Wandering Emperor +1 without targeting its Samurai token, reasoning that the pump was only small temporary pressure. The counter is permanent and the Samurai later became the main clock.

What should have happened

When a planeswalker +1 can place a permanent counter on a real attacker or blocker, the pilot should value that target unless preserving a different mode or avoiding risk is clearly better.

Context

correction target: ["pilot_policy", "atomic_evaluator", "card_note"]
evidence: [{"frames": "148", "game id": "edge_1v1_storm__1_g1_2026070603", "level": 3, "local log": "artifacts/deployed_batteries/edge_case_0521_live_20260706T124234Z/logs/dashboard/edge-case-smoke-deployed-proof-20260706t101310z-edge-1v1-draw-go-vs-storm-g03-level-3/edge_1v1_storm__1_g1_2026070603/game.jsonl", "run group": "edge-case-smoke-deployed-proof-20260706t101310z-edge-1v1-draw-go-vs-storm-g03-level-3", "summary": "Draw-Go used The Wandering Emperor +1 with no target while controlling a Samurai token that later became the main clock."}]
feedback issue key: explicit:wandering_emperor_counter_mode_underweighted_real_clock
recommended source files: ["src/veles/codex_decision_worker/legal_action_context.py", "src/veles/playtest_decisions.py", "../veles-content/strategies/modern/edge_1v1_draw_go_control/1/guide.md"]
root cause: wandering_emperor_counter_mode_underweighted_real_clock
source findings file: reports/edge_case_atomic_eval/0.5.21_live/draw_go_storm_unique_feedback_findings_20260706.json

## What happened In deployed Draw-Go vs Storm g03, Draw-Go used The Wandering Emperor +1 without targeting its Samurai token, reasoning that the pump was only small temporary pressure. The counter is permanent and the Samurai later became the main clock. ## What should have happened When a planeswalker +1 can place a permanent counter on a real attacker or blocker, the pilot should value that target unless preserving a different mode or avoiding risk is clearly better. ## Category - kind: misplay - severity: debatable ## Context - correction target: ["pilot_policy", "atomic_evaluator", "card_note"] - evidence: [{"frames": "148", "game id": "edge_1v1_storm__1_g1_2026070603", "level": 3, "local log": "artifacts/deployed_batteries/edge_case_0521_live_20260706T124234Z/logs/dashboard/edge-case-smoke-deployed-proof-20260706t101310z-edge-1v1-draw-go-vs-storm-g03-level-3/edge_1v1_storm__1_g1_2026070603/game.jsonl", "run group": "edge-case-smoke-deployed-proof-20260706t101310z-edge-1v1-draw-go-vs-storm-g03-level-3", "summary": "Draw-Go used The Wandering Emperor +1 with no target while controlling a Samurai token that later became the main clock."}] - feedback issue key: explicit:wandering_emperor_counter_mode_underweighted_real_clock - recommended source files: ["src/veles/codex_decision_worker/legal_action_context.py", "src/veles/playtest_decisions.py", "../veles-content/strategies/modern/edge_1v1_draw_go_control/1/guide.md"] - root cause: wandering_emperor_counter_mode_underweighted_real_clock - source findings file: reports/edge_case_atomic_eval/0.5.21_live/draw_go_storm_unique_feedback_findings_20260706.json

bstein added the

labels 2026-07-06 17:51:04 +00:00

bstein commented

2026-07-09 06:32:58 +00:00

Verified in Cassandra 0.5.30.

Release proof: source bebd4c7 (Prepare Cassandra 0.5.30 feedback backlog closeout), Jenkins Veles #209 SUCCESS published version-only backend/frontend/sim-worker 0.5.30 images, Titan-IAC 1bf84977 deployed them, live /api/v1/app-config reports backend/frontend/sim_worker 0.5.30, /api/v1/ready is green, backend pod and both frontend pods are Running with 0 restarts, and VELES_SIM_IMAGE is registry.bstein.dev/veles/veles-sim-worker:0.5.30.

Local/source gate on the deployed source: bridge/runtime 42 tests OK; evaluator/audit/policy/API suite 504 tests OK; frontend maybeboard/compact-replay/prompt Playwright 22 tests passed; frontend build and git diff --check passed.

Issue-specific proof: atomic evaluator and misplay audit coverage now detects and rejects The Wandering Emperor +1 with no useful target when a real creature clock exists. Closing.

Verified in Cassandra 0.5.30. Release proof: source bebd4c7 (Prepare Cassandra 0.5.30 feedback backlog closeout), Jenkins Veles #209 SUCCESS published version-only backend/frontend/sim-worker 0.5.30 images, Titan-IAC 1bf84977 deployed them, live /api/v1/app-config reports backend/frontend/sim_worker 0.5.30, /api/v1/ready is green, backend pod and both frontend pods are Running with 0 restarts, and VELES_SIM_IMAGE is registry.bstein.dev/veles/veles-sim-worker:0.5.30. Local/source gate on the deployed source: bridge/runtime 42 tests OK; evaluator/audit/policy/API suite 504 tests OK; frontend maybeboard/compact-replay/prompt Playwright 22 tests passed; frontend build and git diff --check passed. Issue-specific proof: atomic evaluator and misplay audit coverage now detects and rejects The Wandering Emperor +1 with no useful target when a real creature clock exists. Closing.

bstein closed this issue

2026-07-09 06:32:58 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cassandra-alpha/feedback#10