tegwick
bb426b3e9b
The maintainer named a new aspect: clay-borg as a game design tool, with a register for design flaws, questions, results and trial protocols. Structural L on the maintainer-named-high-leverage trigger, and it amends INTENT. Chaos d8=6, no override. The insight is that this is already happening with no home. Five passes have produced ten underdetermined rules points, SOLVE offered on a face-down problem and always inert, GR-A13's wasted SOLVE, GR-E01 unreachable below 5 seats, six provisional scenario defaults, and two scoring modes never played to the end -- every one found by BUILDING the simulator rather than by playing it. A simulator rigorous enough to refuse ambiguity is a design instrument, because it cannot proceed past a rule that does not decide. All of it has been carried in prose in six places and one sat unread in an inbox for four days. The load-bearing rule: a design finding is not admissible without its reproduction. A register that collects opinions would reproduce this project's standing failure -- unexecuted verification -- in a new medium. Recorded as a judgment for the adversarial review rather than assumed: the engine-evolution meta the maintainer also asked about should NOT be built, because evidence/, decisions/, gates.toml and workplans already carry nineteen passes of it with dates, costs and falsifiers. A second register for the same subject is ceremony. The asymmetry is the point -- engine evolution has a home and game design does not. T05 backfills the six known findings as the TEST of the register: one that cannot express findings the project already has is the wrong register, and discovering that after designing it is why the order is survey, review, decide, specify, build. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> |
||
|---|---|---|
| .forgejo/workflows | ||
| benchmarks | ||
| crates | ||
| decisions | ||
| evidence | ||
| games/ground | ||
| history | ||
| research | ||
| scenarios | ||
| specs | ||
| tools | ||
| 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.