Go to file
type-two a74075cda5 Sprint 11 shepherd: C's venturi correction taken, D's two landmines defused
C AND D BOTH LANDED WHILE I WAS IN GATE 2, AND BOTH CORRECT ME.

VENTURI — reverted to axis 2.1 / gain 1.5. C reached the same physics I did,
independently (|dot| means an axis is a line, mod PI), and then went one step
further and caught my reasoning: -1.08 was never a proposed AXIS. It's
dirAt(40), the southerly's HEADING once the change settles. 2.1 is the GAP'S
ORIENTATION — site geometry, which doesn't move when the wind does. They're
different quantities that sit a hair over PI apart only because the gap was
BUILT along the southerly.

So "measured beats authored" was the wrong rule for this question: I'd have
swapped a geometry fact for a weather fact because they nearly coincide, and
the site's axis would silently mean the wrong thing the day someone authors a
storm from another quarter. "A number gathered from the wrong harness" caught
both of us on the same question from opposite sides in one sprint.

Gain reverted too, and that one I simply jumped: it's a balance lever, B's audit
calls it, and C's standing offer is to drop to 1.35 only if no $80 line survives.
B hasn't run. D then measured the site winnable off honest anchors at 98% — so
the funnel isn't killing the line and the gain stays.

D's LANDMINES, both mine, both in gate 2's path:
 · CALM_STORM loaded only because night one HAPPENED to be storm_01_gentle.
   Gate 2 rewrote every night entry. Drop gentle and windTime() throws every
   non-storm frame on "Cannot read properties of undefined (reading 'duration')"
   — naming neither storms, nor calm, nor the week. Now explicit in the preload,
   and the assert calls stormsToPreload() with a gentle-free ladder, because
   asserting it against the shipped NIGHTS passes either way. That's how it hid.
 · boot({site}) was a documented lie that failed INVERSELY — markers on the
   requested yard, world on the week's. Honoured through the week now (seek to
   that site's night), because a site without its night is half a game: no
   client, no brief, no storm, no bank. Plus opts.bank, so D can boot the corner
   block at the $237 they measured instead of night one's $80 and OFF THE JOB.

RATINGHINT — D is right that nothing reads it, and the naive fix is worse than
the bug: honest posts are built from site JSON, never touch adoptAnchor, so
their ratingHint was undefined — and `load > hw.rating * undefined` is
`load > NaN`, always false. The strongest anchors would have become UNBREAKABLE
while the carport became the only thing that can fail: the trap would look like
it works, for the wrong reason, and read as a successful playtest. Every anchor
carries a real number now (DEFAULT_RATING_HINT), pinned, so the wire is safe
before it's made. The wire itself is sail.js — B's — and the ruling is in THREADS.

selftest 306/0/0 (was 304).
2026-07-17 17:51:30 +10:00
.claude Merge Sprint 8; the week is live; balance harness stabilized 2026-07-17 14:02:53 +10:00
docs Add hail juice, plant shred, and a way to screenshot the game 2026-07-17 03:03:54 +10:00
prototype Add side-systems to design doc + playable sail-storm prototype 2026-07-16 20:55:31 +10:00
tools Merge remote-tracking branch 'origin/lane/b' 2026-07-17 16:39:26 +10:00
web/world Sprint 11 shepherd: C's venturi correction taken, D's two landmines defused 2026-07-17 17:51:30 +10:00
.gitignore Add deterministic Blender yard-asset factory 2026-07-16 21:39:52 +10:00
DESIGN.md Add side-systems to design doc + playable sail-storm prototype 2026-07-16 20:55:31 +10:00
LANE_PROMPTS.md Add Sprint 11 plan and lane prompts: prove the corner block, then the job sheet 2026-07-17 16:44:11 +10:00
PLAN3D.md Correct PLAN3D asset inventory; log M0 contract additions 2026-07-16 21:33:42 +10:00
README.md Add README: run, read order, lane model, new-machine setup 2026-07-17 16:49:16 +10:00
server.py Vendor three.js r175, add stdlib dev server and launch config 2026-07-16 21:33:42 +10:00
SPRINT2.md Add Sprint 2 assembly instructions: wire proven modules into one playable storm 2026-07-16 22:24:35 +10:00
SPRINT3.md Add Sprint 3 plan and lane prompts: close the game loop 2026-07-17 01:11:16 +10:00
SPRINT4.md Add Sprint 4 plan and lane prompts: face and water 2026-07-17 02:03:47 +10:00
SPRINT5.md Add Sprint 5 plan and lane prompts: hail and the broom 2026-07-17 02:44:30 +10:00
SPRINT6.md Add Sprint 6 plan and lane prompts: winnable, then a week of nights 2026-07-17 08:54:02 +10:00
SPRINT7.md Add Sprint 7 plan and lane prompts: one truth, then the week 2026-07-17 09:48:23 +10:00
SPRINT8.md Add Sprint 8 plan and lane prompts: ship the week 2026-07-17 11:57:51 +10:00
SPRINT9.md Add Sprint 9 plan and lane prompts: pyrrhic call, $80 win, second site 2026-07-17 14:03:45 +10:00
SPRINT10.md Add Sprint 10 plan and lane prompts: sites are data 2026-07-17 15:12:55 +10:00
SPRINT11.md Add Sprint 11 plan and lane prompts: prove the corner block, then the job sheet 2026-07-17 16:44:11 +10:00
THREADS.md THREADS: Sprint 11 gate 2 — the job sheet, the clean bonus's honest price, and two bugs only looking caught 2026-07-17 17:38:03 +10:00

SHADES — rig it, then survive the night

Geometry/tower-defense: you're a small person rigging shade sails against Australian storms. three.js r175 (vendored, no build step) + a zero-dep Python server. Everything the repo needs is in the repo.

Run it

python3 server.py --port 8801     # any free port
# game:     http://localhost:8801/web/world/index.html
# selftest: http://localhost:8801/web/world/selftest.html   (must be all green)
# 2D proto: http://localhost:8801/prototype/index.html      (the original thesis)

No pip, no npm, no build. Python 3.8+ and a browser.

Read in this order

  1. DESIGN.md — the design canon (what the game is)
  2. PLAN3D.md — the build canon (stack, contracts, lane model)
  3. THREADS.md — the append-only lane log. The project's memory. Read the last few [I] integrator entries to know the current state.
  4. SPRINT11.md — the current sprint (highest-numbered SPRINTn.md wins)
  5. LANE_PROMPTS.md — copy-paste prompts per lane, per sprint (bottom = newest)

The lane model (how this repo is built)

Five parallel Opus agents ("lanes"), each in its OWN clone, on its own branch:

lane owns
A main.js, world.js, camera, hud, week, sites, server — shell & integration, merge shepherd
B sail.js, rigging — cloth sim, economy, balance.test pen
C weather, skyfx, debris, storm/site wind data
D player, interact, ladder, broom — and the designated playtester
E Blender asset factory (tools/blender), models/, textures

Hard rules (they exist because each was earned — see THREADS):

  • One clone per lane. Never two agents in one working tree.
  • Rebase onto latest main before starting; small commits; push your branch.
  • File ownership is the merge strategy; cross-lane needs go in THREADS.md.
  • Selftest green after every landing. Skips must be real. An assert that cannot fail is decoration.
  • All sim code is deterministic (dt, t) — no Date.now, no rAF.
  • Measure, don't reason: the repo's biggest bugs were all "a number gathered from the wrong harness". When two harnesses disagree, find the variable.

Setup on a new machine

Gitea's SSH runs over tailscale (the public host is Cloudflare-proxied, no direct SSH). Add to ~/.ssh/config:

Host gitea.partly.party
    HostName 100.71.119.27
    Port 222
    User git

Then:

git clone git@gitea.partly.party:monster/shades.git ~/Documents/shades
for L in A B C D E; do
  git clone git@gitea.partly.party:monster/shades.git ~/Documents/shades-lane$L
  git -C ~/Documents/shades-lane$L checkout -B lane/$(echo $L | tr 'A-Z' 'a-z') origin/lane/$(echo $L | tr 'A-Z' 'a-z')
done

~/Documents/shades is the integration checkout (main; where merges and sprint docs happen). The five shades-lane* clones are where lane agents run.

Sprint cycle

  1. Fire lanes with the newest prompts at the bottom of LANE_PROMPTS.md (Lane A usually first if the sprint gives it rulings/blocking items).
  2. Lanes work, push their branches, log in THREADS.md.
  3. Integrate in the main checkout: merge origin/lane/{e,c,b,d} (THREADS.md conflicts resolve keep-both-chronological; real code conflicts get read), run selftest, play the result, write SPRINT(n+1).md + prompts, push main AND fast-forward all five lane/* branches to main.