tegwick
0b8599bd88
Some checks failed
ci / check (push) Failing after 4s
Five things worth their time, four of them asks rather than statements: F29 SCN_01 and SCN_02 are the SAME BOARD -- identical suit and value at every priority, every cell matching exactly. Not called a defect (a reskin is legitimate) but "four scenarios" is three boards. Asked whether it is intended. F30 SCN_04 is materially harder at 2p: 52/100 against 67 and 73, with every other parameter held by the edition itself -- same deal shape, same 6 available points, same threshold, same starting Stress. The lone difference is that it is the only 2p deal needing two of one suit. Causation explicitly NOT claimed; the falsifier is stated. Sensitivity: at 4p SCN_04 is 97 against 94/99, so it is not the hard board there. The modes finding, corrected in their favour: we previously reported the three modes produced identical play. That was OUR INSTRUMENT, not their game -- the bot never read the Mode card. With a mode-aware bot, group success is unchanged in 34 of 36 cells but coalition size moves by half again at 4p. So the modes decide the distribution of the win and the threshold decides survival independently of it. F28 (mastery counts cards where the shared score counts points) and F26 (a package that adds a FILE is invisible to a consumer) promoted to reported -- both need their ruling, neither changed on our side. F17 and F26 move raised -> reported now that they are in a delivered report. The register crossed the ~400-line loadability limit, so prose for CLOSED findings moved to FindingRegister-closed.md. The rows are untouched and `make design` still reads one file -- ADR-0012 D5's reasoning about mixing open and closed applies to files too. Report left UNCOMMITTED in ground-game: their tree has live uncommitted work from their own agent. 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.