tegwick
74d9b8ef73
Some checks failed
ci / check (push) Failing after 3s
Scoped to what CB-WP-0005 T02 measured rather than what CB-RES-0004 predicted. The survey diagnosed three absent kernel rules; M-D1-MUT found that 8 of 14 acceptance rows have no instrument behind them at all. Phase A instruments the unmeasured rows, starting with AM-6 — nothing in the workspace compares any number to 100,000 events/s, the project's headline throughput claim, reported as "met, 16.5x". Phase B carries the kernel work deferred unstarted from CB-WP-0005 Phase C. That order is the point: the previous pass built a fix before its instrument existed and the instrument then contradicted the fix's premise. T01 names its own trap up front: a timing assertion in CI is flaky by nature and the usual response is to loosen it until it never fires, which would reproduce exactly the defect being fixed. The threshold is pinned far below measured, states its headroom in the failure message, and loosening requires an ADR. T04 notes an incentive worth blocking early: ADR-0005 predicts own-source growth from Phase B, so AM-4c will move against us. Setting its threshold after seeing that movement is the retarget InnerLoop §Step 4 forbids, so it is set before Phase B or not at all. T09 asks the question this pass is positioned to answer: M-D1-MUT does not remove a manual path — writing a weak mutation is exactly as easy as writing a strong one and the harness cannot tell them apart. CB-WP-0005 produced two no-op mutations on its first attempt, so the failure mode is demonstrated. And it fails in the dangerous direction: a weak mutation does not miss a defect, it indicts working code. CB-WP-0005 T04-T06 are marked deferred rather than deleted, with their analysis intact, so the trail from prediction to contradiction to re-plan stays readable. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| benchmarks/baselines | ||
| crates | ||
| decisions | ||
| evidence | ||
| games/ground | ||
| history | ||
| research | ||
| scenarios/ground | ||
| specs | ||
| tools | ||
| workplans | ||
| .custodian-brief.md | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| clippy.toml | ||
| facts.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.