|
Some checks failed
ci / check (push) Has been cancelled
Policy::choose takes the whole GroundState -- every face-down Problem's suit and value, every seat's hand -- which is exactly what project() exists to withhold. No shipped policy reads it, but the first thing a competitive policy must do is VALUE a Problem, and value is the hidden field. The trap goes live on the first line of the F27 work. Established behaviourally rather than by narrowing the trait: vary only what the seat cannot see, and the choice must not move. That binds every policy including ones written later and outside this crate, without their cooperation. The mirror of ADR-0013 D1 -- same kernel, two searches, opposite permissions, discriminated by WHEN the question is asked; a policy plays from inside an information set, so retrospective permission would be strategy fusion. Running the control found two defects IN THE CONTROL: 1. The rearrangements rotated hidden values 2<->3 together, leaving max invariant -- so the deliberate peeker, which ranks by the largest hidden value, was not caught. A control whose variation is invariant under the statistic a violator reads is not a control. 2. It accused `random` of peeking, because it reused one policy instance and compared a first call against a fourth. It takes a constructor now, so every variant is judged from identical policy state. Both are a difference in output read as evidence about hidden state -- the wrong-subject family, found twice inside a control written to detect wrong subjects. Three mutations, three red. The control is proven against a deliberate violator before being trusted about compliant policies. 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.