From 1944b21b191acbb24d897c55b25ebf403ee48a13 Mon Sep 17 00:00:00 2001 From: LANE-SIM Date: Fri, 17 Jul 2026 18:37:25 +1000 Subject: [PATCH] [sim] round 3 NOTES Confirms the units conversion (bufferCap 240 = 8.0s of cover at a 30/s deficit) and reports scram survival: first scram t434, restart t934, ~718-tick duty cycle, ZERO brownout ticks across 20k, melt rate unchanged. For the orchestrator: - heat semantics need a one-line ruling. heatPerTick is GROSS in my model (net = heatPerTick - coolPerTick). DATA's committed 0.0025 against the 0.004 default nets negative -- the decoder could never scram. Their in-flight 0.0033/0.001 works, so we agree by luck of timing. - the codex's literal bloom loop is not expressible with per-grade recipes - asic-cooler does nothing without a spatial heat mechanic - my sim code landed inside 45003db [ui] REMOVE mode: the shared tree has one git index, and an add-everything commit in another session swept it. Not a UI ownership violation. Suggest a no-`git add -A` rule. Co-Authored-By: Claude Opus 4.8 --- fktry/lanes/LANE-SIM.md | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/fktry/lanes/LANE-SIM.md b/fktry/lanes/LANE-SIM.md index 13fa59b..7257693 100644 --- a/fktry/lanes/LANE-SIM.md +++ b/fktry/lanes/LANE-SIM.md @@ -348,6 +348,15 @@ BLOCKED/BROKEN ids. Either accept the escalator reading, or that's a schema change. - Ownership wart is gone: `data/validate.test.ts` is staged by DATA and `src/sim/**` is purely mine again. Thank you. +- **My round-3 sim code is committed inside `45003db [ui] REMOVE mode`, not under a `[sim]` + commit — please don't read that as a LANE-UI ownership violation.** All five lanes share one + working tree and one index. I had `src/sim/**` staged; LANE-UI's session ran an + add-everything commit in the same repo a moment later and swept my staged files in with + theirs. By the time my own `[sim]` commit ran there was nothing left to commit, and 45003db + was already pushed. The code is correct and complete in the tree (48 sim tests green, tsc + clean, verified in-browser); only the attribution is wrong, and rewriting pushed history + under four concurrent sessions would do more damage than the mislabel. Flagging it so your + per-lane diff doesn't fire. See PROPOSAL. CONTRACT REQUEST - None. v3 covered everything. @@ -360,6 +369,12 @@ PROPOSAL with leftover sims and got anywhere from 59× to 12× for the *same* build; a fresh page gives 74.9× consistently across three runs. The numbers were never wrong so much as noisy — if you ever want perf tracked properly it should be a headless benchmark, not a browser probe. +- **The shared working tree needs a commit rule.** Five sessions share one repo *and one git + index*, so any lane running `git add -A` / `git commit -a` silently commits whatever another + lane has staged at that instant — that's how my sim work ended up inside a `[ui]` commit this + round, and it'll keep happening. Cheapest fix: a standing rule that lanes only ever + `git add ` and never `-A`/`-a`/`.`. Failing that, `git worktree` + per lane would make it structurally impossible. NEXT (round 4 if asked) - HF dust piles + mosquito swarms — the seeded RNG is still unrolled, and save/load already