tegwick
3a47e263df
Some checks are pending
ci / check (push) Waiting to run
Declaration 1 of chaos window 3 (opened by ADR-0017), tier M, chaos d8=7, no override. Seven claims in this project have been wrong the same way, and the workplan tabulates all seven with what caught each. MEASURED BEFORE PROPOSING: facts-check reports 62 untagged literal copies and fails on none, which is a real drift surface it names and does not close. CLOSING IT WOULD HAVE CAUGHT AT MOST ONE OF THE SEVEN. Instance 1's denominator WAS a registry fact and WAS correct -- the error was that AM-4a does not cover the code. Four others were fresh measurements with no registry key. A tag proves a number came from somewhere; it cannot prove the somewhere was the right place. Named as separate work rather than bundled, because bundling would let this pass claim a victory it did not win. What did work: every instance was caught when the number was computed a SECOND TIME by something with a different purpose. Two of them share a sharper property -- the claim was tested against a variation. #4's cost FELL as branching ROSE, which no per-node cost can do, and the tell was in the published output. #5's win rate was attributed to the game, and a second policy on the same deals gave 0% where the first gave 100%. So the rule generalises what this project already builds after each instance (the policy panel, the attack-value sweep) and requires it before: a measured claim must name the variable it depends on and show the measurement moving with it. A number that does not move when its subject moves is measuring something else. HONEST YIELD: 3 or 4 of 7, and it catches the two that travelled furthest. It does not catch a count never made, or a claim that is not a number. Claiming it closes the family would be the family's own error applied to itself. T03 requires the lint to fail on a real row by mutation, and to say in its own output that it checks PRESENCE and not ADEQUACY -- so nobody reads a green lint as 'the claim was verified'. 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.