tegwick
8ae68195b8
Some checks are pending
ci / check (push) Waiting to run
ModuleAwarePolicy reads the RESOLVED Rules -- one policy, not one per module. H2AwarePolicy would have been the blob schema 2 exists to retire, rebuilt a layer up; reading Rules means a two-module configuration gets both terms and a future module is one arm here rather than a new policy per combination. Two terms, both reading the table: prefer the Problem whose Stress falls on me (problem_stress.scoped), and treat ATTACK as a Stress tool at the gate (attack_relief.self_soothe_ge4). stress_scope and the owner marker are public regardless of the card's face -- the H2 rules place the marker ON the card -- so it is blind by construction. THE CONTROL I CLAIMED WAS REAL WAS VACUOUS, AND MUTATION SAID SO. "Under the baseline the two must be identical" swept fresh deals across 36 combinations, and forcing the scope term to fire regardless of configuration left it GREEN. At a fresh deal only the Surface Problem is face up, so exactly one SOLVE is legal and no ranking term can move the argmax. The control could not distinguish the property from its negation. Both tests now use a BUILT position -- two face-up, unclaimed, equally valuable Problems differing only in scope -- under H2 for divergence and under the baseline for the control. The mutation goes red there. That is also a finding about the module: the scope term is INERT at round-one positions, so anything measuring H2 with round-one-heavy play is measuring a mechanism that has not started. Recorded, not tuned away. Also: CB-WP-0048 was `active` with every task closed; loop-lint's lifecycle rule caught it. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| bot.rs | ||
| catalog.rs | ||
| config.rs | ||
| edition.rs | ||
| lib.rs | ||
| record.rs | ||
| search.rs | ||
| view.rs | ||