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> |
||
|---|---|---|
| .forgejo/workflows | ||
| benchmarks | ||
| crates | ||
| decisions | ||
| editions | ||
| evidence | ||
| games/ground | ||
| history | ||
| research | ||
| reviews | ||
| scenarios | ||
| simulators | ||
| specs | ||
| tools | ||
| trials | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| clippy.toml | ||
| facts.toml | ||
| gates.toml | ||
| INTENT.md | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
| rust-toolchain.toml | ||
| WORK-RECORDS.md | ||
clay-borg
A rebuild from scratch simulation and games engine framework set up to assimilate and optimize techniques and implementations useful for games, simulations, robotics.
Licensed under the Target Revenue Source License (TRSL V1C1) — see LICENSE; canonical text lives in the org's target-revenue repository.
Running the gates
make all # every gate, from a clean shell
make -C /path/to/clay-borg all # …or from any other directory
There is no environment setup step. No cd, no export PATH, no
activation script. make locates the repo from its own path and cargo
from the standard rustup locations; the Python tools do the same via
tools/repo.py. The only prerequisites are a rustup toolchain and Python
3.11+.
This is deliberate and enforced: make env-test runs every tool from /
with a PATH containing no cargo, and make all includes it. CB-RES-0003
measured 84 agent turns and $15.33 spent prefixing commands with cd and
export PATH before that friction was fixed at the root (CB-WP-0004 T01).
Other useful targets: make cost (spend per task), make cost-budget
(spend since the last commit), make cost-mix (mechanical vs judgment
turns), make loop-lint (executable InnerLoop rules), make self-tests
(every tool's positive control).
GROUND
The first product vertical is a virtual tabletop implementation of GROUND — A Game of Bonds and Rivalry: DARVO Edition. The boardgame itself (rules, editions, content) is at home in the sister repository ground-game — that repo is authoritative for what GROUND is; clay-borg implements the engine that runs it.