0041 answers what is true of the engine as a game-theoretic object before anything is built on it. CB-RES-0009 found the EFG is the interchange format between describing a game and analysing it, and that we already have most of one — the journal is the history, Outcome the payoff, and project(Viewer::Player(seat)) the information partition. Three gaps remain, and perfect recall is first because CFR and exploitability both assume it and nobody has checked ours. The workplan deliberately builds no port: creating a capability port is a tier-L trigger and this is M, so T04 decides whether to build one and declares it separately. T01's control includes that the answer may be NO, which would make Track B's adoption unsound as it stands. 0042 implements H2, which is ground-game's direct answer to our H1 reading. Unclaimed Problems now tick only the seats in scope — global, personal (the owner), or bond (the owner's Bond network over Bond edges only, degree 0 falling back to personal) — assigned by hidden priority, so 2p never has the bond card in play. It explicitly does not stack with H1. H2 is bigger than H1 was: it needs variant-scoped edition data (H2 overrides Problems.csv with a stress_scope column, and ours is an include_str! constant), per-Problem ownership which is new state reaching the hash and every recording, and Bond-network reachability. The controls name the likely defects in advance: traversing Rivalry edges, applying stacking once, forgetting the degree-0 fallback, and ownership silently becoming a permission to SOLVE. Chaos window 4 opens: d8 = 5 and d8 = 4, no overrides. Window 3's verdict is still owed. 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.