coulomb/clay-borg
4
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
clay-borg/trials/2026-08-06-2252.yaml

151 lines
2.3 KiB
YAML
Raw Normal View History

CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
scenario: ground/cb-play-session
description: recorded by cb-play (CB-WP-0008 T02)
covers: []
provisional: false
provisional_owner: ''
provisional_raised: ''
ruled: ''
ruled_by: ''
ruled_note: ''
encodes_u_item: ''
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
seed: 2
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
setup:
players: 3
preset: standard-3p
patch: {}
commands:
- actor: P1
cmd: select_action
args:
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
action: GROUND
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P2
cmd: select_action
args:
action: SOLVE
problem: 1
- actor: P3
cmd: select_action
args:
action: SOLVE
problem: 1
- actor: SYSTEM
cmd: reveal
args: {}
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
- actor: P1
cmd: choose_ground_mode
args:
choice: protect_problem
mode: OU
problem: 1
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: SYSTEM
cmd: resolve
args: {}
- actor: SYSTEM
cmd: end_round
args: {}
- actor: P1
cmd: select_action
args:
action: INVESTIGATE
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
problem: 2
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P2
cmd: select_action
args:
action: INVESTIGATE
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
problem: 2
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P3
cmd: select_action
args:
action: INVESTIGATE
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
problem: 2
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: SYSTEM
cmd: reveal
args: {}
- actor: SYSTEM
cmd: resolve
args: {}
- actor: SYSTEM
cmd: end_round
args: {}
- actor: P1
cmd: select_action
args:
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
action: INVESTIGATE
problem: 3
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P2
cmd: select_action
args:
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
action: SOLVE
problem: 2
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P3
cmd: select_action
args:
action: SOLVE
problem: 2
- actor: SYSTEM
cmd: reveal
args: {}
- actor: SYSTEM
cmd: resolve
args: {}
- actor: SYSTEM
cmd: end_round
args: {}
- actor: P1
cmd: select_action
args:
action: SOLVE
problem: 3
- actor: P2
cmd: select_action
args:
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
action: INVESTIGATE
problem: 4
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P3
cmd: select_action
args:
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
action: INVESTIGATE
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
problem: 4
- actor: SYSTEM
cmd: reveal
args: {}
- actor: SYSTEM
cmd: resolve
args: {}
- actor: SYSTEM
cmd: end_round
args: {}
- actor: P1
cmd: select_action
args:
action: SUPPORT
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
target: P3
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P2
cmd: select_action
args:
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
action: SOLVE
problem: 4
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: P3
cmd: select_action
args:
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
action: SOLVE
problem: 4
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
- actor: SYSTEM
cmd: reveal
args: {}
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
- actor: P3
CB-WP-0029: the tokens on the table — declare and register Declaration 12 of chaos window 2, which CLOSES IT. Structural M (imports another edition file under AM-4's budgets), chaos d8=4, no override. Tokens.csv turns out to carry more than names. Every token has a `quantity` -- 6 Protection, 5 Denied, 12 relation links -- and a component count is a limit a simulation does not have unless it is told. protection is saturating_add(1) at lib.rs:986 with no upper bound, against an edition that ships six tokens for six players. T03 measures whether that matters rather than assuming either way. And `sides` is the second interesting column: Freedom and Focus/Blame are each ONE DOUBLE-SIDED TOKEN, not two states. The engine holds Focus in a map and Blame in a list; whether those can disagree with a single physical token is worth checking. T03 is shaped against a specific error: whatever it finds is a FINDING, not a fix. A component limit the rules do not state is underdetermined and belongs to ground-game, and the engine must not start enforcing a bound nobody ruled. CB-WP-0023 exists because SOLVE was offered where it could not act; inventing a limit is the same error in the other direction. The workplan also names the window-2 verdict as DUE. Its retirement condition was untestable throughout -- eleven declarations, zero 8s, zero overrides -- and recording that is a change to how the loop constrains itself, so it is its own tier-M pass rather than a task here. Named so it is not lost between passes, which is how the ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:45:41 +02:00
cmd: respond_to_support
args:
response: accept_bond
- actor: SYSTEM
cmd: resolve
args: {}
- actor: SYSTEM
cmd: end_round
args: {}
expect:
events: []
state: {}
rejects: []
CB-WP-0029 T01-T03: components you can count, and a supply that does not bind ADR-0016, Tokens.csv vendored, tracks and discs on the table, and a supply audit that found nothing and says so. T03 MEASURED BEFORE T01 DECIDED. 750 games, 2-6 seats, greedy and random: Protection reaches 1 per seat and 2 on the table against a supply of 6; Denied 3 of 5; relation links EXACTLY 12 OF 12 and never more; Focus/Blame 0 conflicts. The link row is the interesting one -- GR-L01's two-slot rule IS the twelve-token supply written twice, which is the shape of a supply needing no separate enforcement. AND THE FIRST VERSION OF THE FOCUS/BLAME CHECK WAS WRONG. It compared a seat's own placed Focus against its OWN blame_from -- but that list holds OTHER players' discs, so they are different tokens. It reported 2 conflicts; corrected, it reports 0. Fifth instance of this project's recurring defect, a number computed correctly about the wrong subject, and the first caught before it left the repo rather than by a reviewer. D2: a token is a VIEW, not a type. The aggregate gains no `Token` -- adding one would create a second source of truth for Stress, and the first time they disagreed the bug would be invisible because both would look internally consistent. D3: quantity does NOT bind, and the reason is not the measurement. A component limit the rules do not state is not a rule. Refusing a seventh Protection token would enforce something nobody ruled -- CB-WP-0023's error inverted: SOLVE was OFFERED where it could not act; this would REFUSE where the rules allow. The check ships as a standing control, so a future violation becomes a question for ground-game (does the box bound the game, or do the rules?) rather than a bound the engine invented. Registered as F22, withdrawn: a stated negative, because a survey that finds nothing and leaves no trace cannot be told from one never run. D4: Stress on a 0-5 track that turns red at 5 where DARVO arms, DARVO on OFF/DENY/ATTACK/REVERSE, Freedom as the two-sided disc the edition says it is, Protection and Blame counted, Lead and Round on the table. Two tests broke on token discs and both were FIXTURE defects: seat_centres matched every <circle> and track stops are circles. Seats now carry class="seat". The table height limit went 460 -> 500 as a CORRECTION, not a concession. 460 had no derivation; 500 does -- ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging was 620. CB-WP-0021 T06's rule is to fix the measurement rather than lower the floor, and an underived number is a measurement defect. make all: exit 0. 66 render tests, 26 cb-play. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-07 09:54:20 +02:00
state_hash: f227bb9e0c62f91735508514b5f0d51f6d59b48b68619b9ae641d25f191aa01b
Reference in a new issue Copy permalink