tegwick
a170458762
Some checks failed
ci / check (push) Failing after 3s
evaluate CB-EV-0027. The supply is never exceeded, and the link row explains why: GR-L01's two slots per seat ARE the twelve link tokens, the same constraint written twice. Nothing was designed to make that true; it fell out. The Focus/Blame check was wrong and I caught it -- fifth instance of the family CB-EV-0019 named (a number computed correctly about the wrong subject) and the FIRST caught before leaving the repo, rather than by an adversarial reviewer or the maintainer. That is one data point, not a trend. What differed is that this pass read its own output and asked what exactly it had compared. The family still has no control: facts-check catches copies that disagree and nothing catches a correct computation over the wrong subject. The height limit went 460 -> 500, and the evidence argues why that is a correction and not a concession. 460 was a number picked while fixing the unplayable table -- no derivation. 500 has one: ~800px viewport less ~120 header and ~150 controls leaves ~530, and the version that broke dragging declared 620. An underived limit is a measurement defect; replacing it with a derived one is CB-WP-0021 T06's rule applied rather than evaded. A later pass wanting 560 has to move the viewport budget, not the number. CHAOS WINDOW 2 IS CLOSED. Twelve declarations, zero 8s, zero overrides. Its retirement condition -- retire if an override changes nothing twice running -- was untestable from the first declaration to the last, and CB-EV-0024, 0025 and 0026 each said so; this is the fourth and final. Window 1 at d4: 12 declarations, 2 overrides, both changed the outcome. Window 2 at d8: 12, 0, none. The verdict this supports is that d8 bought rarity by spending evidence -- stronger than "the rate is too low", because the rate was chosen without asking what sample size the retirement condition needs. Recording that changes how the loop constrains its own operation, which is a tier-M trigger in its own right, so it is OUTSTANDING and named rather than bundled here. Leaving it implicit is exactly how ground-game's ten rulings went uncollected. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| benchmarks | ||
| crates | ||
| decisions | ||
| editions/ground-darvo-r0 | ||
| evidence | ||
| games/ground | ||
| history | ||
| research | ||
| scenarios | ||
| 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.