tegwick
fe772eebc9
Some checks are pending
ci / check (push) Waiting to run
The maintainer's ask: game interface left, meta and commentary right, with comments bound to game state so a test player's perception, confusion and reasoning become reviewable signal. Declared M (chaos d8=7, no override, declaration 10 of window 2). It touches two canonical interfaces: ADR-0007 D5's input contract, which currently admits only raw pointer facts, and the recorded-session format, which is deny_unknown_fields -- CB-WP-0026 just proved that bites. FRAMED AS GameDesign §5's TRIAL PROTOCOL MADE ERGONOMIC, because that is what it is. The protocol already exists and nobody would use it as written: it asks the player to reconstruct their reasoning afterwards, from memory, in a sibling file. A comment typed while the position is on screen is contemporaneous, bound to something replayable, and captures the one class of signal no gate in this project can see -- confusion and frustration. The reason it is worth more than a comment box: GameDesign §3.1 makes a note unreportable until it has a reproduction, and three findings are stuck there now (F12, F14, F15). A comment bound to a recorded state, plus the recording, is the cheapest reproduction a play-derived observation can have. So the pass closes the register's input path for findings that come from playing rather than from building. The failure it must not reproduce is named up front: a pile of prose nobody reads is this project's signature defect -- the four-day unread message, the ten uncollected rulings. Storage is not the deliverable, surfacing is, and T04 carries it. T01 (ADR-0014) must decide where comments live, what the page may send (D5's transport widens from two ids to arbitrary user text -- amended or merely scoped?), what binds a comment to a position, and the retention question this project has not faced: these are the maintainer's own words about his own game, one will eventually be unflattering, and whether they travel to ground-game needs deciding before any are written. T03 notes that esc() is about to face its first hostile input -- until now it has escaped suit names. loop-lint: no findings. 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 | ||
| 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.