#173 CLOSED-AUTHENTIC with measurements: chicken-walker seek-4 overheat is the machine's own balance -- heat plumbing byte-identical on all 18 chassis (loop 5 = GenD+Myomers only, the MINIMUM load; walkers carry the LARGEST banks), no speed-dependent cooling exists in the binary, and the decisive control is a HUMANOID Avatar cooking identically in the same speed class (14.3s vs vulture 13.9s). Manual speed cross-check kills the last defect avenue: the machine's walkers were PRINTED FASTER than the port runs them. Ticket's 16x premise corrected (gears 1-3 heat-identical; seek-4 = 2.04x). The authored lever validated: loop-5 valve at detent 50 = 2.7x capacity = sustained gear-4 vulture; the detent cycle 1->5->50->0 wrap explains 'boosted and still cooked'. Oracle's spawn-discharge claim CONFIRMED end-to-end. Field guide gains section 2B (sprint-gear doctrine + valve trick + wrap warning + the 15-second era question); Loki-family repro predicted for Friday. Residual [T3]: gait-surge |a| at render cadence vs the pod's 28Hz -- one bench + one era answer close it

This commit is contained in:
Joe DiPrima
2026-08-13 17:31:12 -05:00
parent ef90b6af8c
commit 47826018cf
2 changed files with 170 additions and 7 deletions
+126 -7
View File
@@ -342,17 +342,136 @@ speed in the spike frames. The calibration facts above (constants byte-exact, d
kinetic term) all STAND; the in-life governor (running hot at sustained top speed derates the
myomers) is authentic and remains.
## Spawn-discharge loop heat + per-chassis generator bias (night-16 field, 2026-08-12) [T3 field-observed, mechanism plausible-authentic]
## Spawn-discharge loop heat + per-chassis generator bias — ✅ CONFIRMED (2026-08-13, #173 bench lane) [T2 live receipts + T1 authored data]
Oracle's explanation for the long-standing "missiles cook off on one side first" reports
(Lynx): at spawn ALL weapons start discharged, and the initial CHARGE of the energy weapons
dumps heat into their loops; generator assignments are biased per chassis (Avatar: BOTH large
lasers on GeneratorA), so that side's loops start hot and a missile launcher sharing the side
cooks off first even if the player fires only missiles. Not yet verified against the authored
data -- verify via BTL4.RES generator/loop assignments before treating as established. [T3]
cooks off first even if the player fires only missiles. **All three links verified:**
(1) *Weapons spawn discharged* — Emitter ctor @004bb120 AND ResetToInitialState @004ba4d0 both
seed `currentLevel=0` + weaponAlarm Loading [T1]; (2) *charge heat lands in the powering
generator* — `TrackSeekVoltage` @004ba838: `src->pendingHeat += seekRate² · dtScale · dt`,
and the generator conducts to its authored condenser (GenA→C1, GenB→C2, GenC→C3, GenD→C5,
uniform all 18 variants) [T1]; (3) *the Avatar bias is authored* — BTL4.RES avatar chain:
ERLLaser_1 AND ERLLaser_2 both `VoltageSource=GeneratorA` (plus ERMLaser_1) [T1].
**Live receipt** (solo avatar, BT_HEAT_LOG, ZERO shots fired, first 5 s census,
`m173_ava_s4.log`): GeneratorA T=559 load pegged 1.0 vs GeneratorC T=172 / GeneratorD T=79;
Condenser1 (GenA's loop) 390→459 while C4/C6 sit at 75; and **LRM10_1 (authored to loop 1)
reads 144 vs LRM10_2 (loop 3) at 94** — the asymmetric missile-side heating with no trigger
pulled. Loops also BACK-HEAT their weapons (ConductHeat is two-way): vulture's ERMLasers on
hot loop 2 climbed 76→182 in 10 s, zero firing (`m173_vul_s1.log`). [T2]
Related open defect/question: **#173** -- Vulture (and per Oracle ALL large chicken walkers)
cannot run seek-4 myomers without immediate overheat, loop 5 pegged, heat only sheds near
standstill (Elengil; Oracle repro). Investigate myomer heat rate + loop-5 capacity vs authored
data for those chassis; authored-balance vs port-artifact undecided. The myomer drive-heat
FORMULA is verified faithful (#137, above) -- if the rate is right, the question moves to the
authored loop capacity / condenser assignments.
standstill (Elengil; Oracle repro). ⚑ SETTLED 2026-08-13 by the three lanes below (authored
data + cooling-side audit + live bench matrix): AUTHENTIC authored balance, reproduced and
quantified; one bounded [T3] severity residual (accel-term ring cadence) and the locomotion
top-speed cross-check remain flagged. See the BENCH lane block for the numbers.
## #173 COOLING-SIDE AUDIT (2026-08-13) -- the binary heat chain leans AUTHENTIC [T1 data/formulas, T2 equilibrium]
Full authored heat-family dump (content/BTL4.RES type-17 walk, scratchpad heatscan3.py) + the
dissipation chain from the decomp. The chain: Myomers -> Condenser5 -> Bank -> ambient-300.
- **Cooling is authored CHASSIS-FLAT** [T1]: every one of the 18 variants streams IDENTICAL
condensers (k=315000, mass=420000, refrig=3, degT=failT=2000), myomers (k=190000, mass=250000,
velEff .995/accEff .8, gears 0.3/0.5/0.7/0.9999 rec 2 at res+0x198..0x1AC), generators (rated
10000, GeneratorD AND Myomers both sinkIdx=8 = Condenser5 on ALL chassis), reservoir, and bank
(k=231000, mass=1.39e6) -- the ONLY per-chassis field is bank HeatSinkCount (owens 5, blkhawk 6,
mad2 10, mad1/thr1/sunder 13, madcat 14, avatar/loki 15, vulture/vul1/lok1/lok2 18, thor 28,
snd1 30), and at balanced valves it moves max shed by <2% (bottleneck is condenser->bank).
moverMass (type-15 GameModel +0x0): owens 35k, blkhawk/VULTURE 60k, loki 65k, avatar/thor 70k,
madcat 75k, sunder 90k. **No per-chassis gear cap exists** (shared 4-gear table + sentinel).
- **NO speed-dependent cooling anywhere in the binary** [T1]: full operand walks of
ComputeHeatFlow @004ad9ec (dt, k, coolantLvl/cap, flowScale, masses only), the bank radiator
@004ae73c (adds zone damage + frozen ambient-300 target), UpdateCoolant @004adbf8 (damage-driven
leak). No airflow term. "Cools only near standstill" = generation (~0.07·m·v²·ratio²/s kinetic
+ 0.2·m|v||a| gait term) vs a FIXED-capacity chain. Authentic behavior, not a port break.
- **Seek-4 heat multiplier is 2.04x, NOT 16x** [T1]: ratio = gears[cur]/gears[rec] CLAMPED >= 1
(@004b8d18), so gears 1-3 are heat-identical and gear 4 = (0.9999/0.7)^2 = 2.04x -- times the
supercharge speed feedback (v x1.4284 -> v^2 x2.04) = ~4.2x total at unrestricted cruise.
- **Equilibrium math validated against live data** [T2]: linearized per-second stage rates
(massScale=3 refrigeration included): myo->cond 44.4k/K-of-dT, cond->bank 28.8k x valveShare x
(2.73·Tc - 0.91·Tb), bank->ambient 23.1k x hsCount x (Tb-300). Solver (scratchpad equilib.py)
reproduces the measured BLH gear-4 governed equilibrium (predicted 1783 @ v=44 vs measured
1718-1770, seek4.log) and the radiator shed line. Balanced-valve chain capacity ~= 1.9e7/s at
Tm=2000 on EVERY chassis; **loop-5 boost (detent 50) = 2.7x capacity (5.07e7/s)** -- the
authored lever that sustains unrestricted gear-4 on a vulture (0.67-0.83x of capacity).
- **Why the big chicken walkers cook**: gear-4 unrestricted generation / failure-line capacity =
1.77x for blkhawk (hovers at ~1770, keeps moving) vs 2.2-2.8x for madcat/thor/vulture-if-faster
(blows THROUGH failT 2000 -> myomers fail -> speed+turn freeze; ~6 s to degT, ~12 s to failT
from cold; Condenser5's MFD bar pegs in ~3 s since load full-scale ~= T 300). GeneratorD shares
loop 5 everywhere, so a pegged loop back-heats it toward its own trip -- the freeze amplifier.
- **Residual for the verdict** [T3]: vulture mass = blkhawk mass (60k), so the field split
vulture-vs-blkhawk requires the vulture's CLIP-DERIVED base speed (mech+0x34C, run-cycle avg
root speed @0x4a80d4) and/or gait |a| bob to exceed the BLH's measured 43.6 u/s -- at equal
speed the two compute identically. Type-15 gamedata splits 33-36/43-44 into exactly two motion
groups (avatar/madcat*3/sunder*2/thor*2/vulture*2 vs blkhawk*2/loki*3/owens*2) [T4 field
meaning]. Bench lane: measure vulture v/|a| at gear 3/4 vs BLH.
**#173 AUTHORED-DATA lane result (2026-08-13) [T1]: the heat/cooling plumbing is
BYTE-IDENTICAL across ALL 18 mech variants** (parsed from `content/BTL4.RES` type-17
SubsystemModelStream, parser `scratchpad/night17/myoaudit.py`; walk verified byte-exact --
every stream consumed to the byte via the self-describing `subsystemModelSize@+0x24`).
Every chassis gets the SAME: Myomers record (velEff 0.995 / accEff 0.8 / tmass 2.5e5 /
cond 1.9e5 / seekV 0.3/0.5/0.7/0.9999 rec 2, hsi=8→Condenser5, vsi=13→GeneratorD), six
identical Condensers (tmass 4.2e5, cond 3.15e5, refrig 3.0, degT=failT=2000), identical
Generators (rated 10000 V, tap 6, GenD always hsi=8→Condenser5), identical Reservoir
(cap 20, squirt 0.5). Loop 5 = GeneratorD + Myomers ONLY on madcat/vulture/vul1/thor/
thr1/loki/lok1/lok2 (the fielded chicken walkers carry the MINIMUM possible loop-5 load);
the variants with extra loop-5 weapons are mad1 (2 MLaser), mad2 (ERPPC), ava1 (2 ERMLaser),
own1 (AFC25), sunder (2 MLaser) -- no walker bias. Manual COOLANT LOOPS pages print the
same GenD+Myomers loop-5 topology for every mech [T1 primary]. The ONLY chassis-varying
heat inputs are moverMass (type-15 GameModel +0x00: owens 35t, vulture/blkhawk 60t, loki
65t, thor/avatar 70t, madcat 75t, sunder 90t) and top speed/accel (manual stat sheets:
Loki/Thor 143 N / 182 SC kph, Vulture ~175 N [OCR-fuzzy T3], Owens 154, Blackhawk ~190
[OCR-suspect]; maxAccel authored: madcat 20, loki 15, vulture/thor/avatar/sunder 10,
blkhawk 30, owens 50). m·v² through the verified formula puts the 60-75 t / 143-175 kph
walkers at ~1.6-2.2x the light-humanoid kinetic heat rate into the SAME fixed-size loop --
seek-4 zero-cooling degradation bound ~7-10 s (vulture worst) vs ~16 s (owens). Verdict
lean: AUTHENTIC authored balance (fast-heavy chassis cook by design); residual port-defect
risk sits ONLY in the runtime velocity magnitude (locomotion lane -- cross-check the port's
per-chassis top speed vs the manual print figures; bench lane #9).
**#173 BENCH lane result (2026-08-13) [T2 measured, live receipts]: Elengil's report
REPRODUCED and quantified; the equilibrium is a GOVERNOR THERMOSTAT, and it is chassis-blind
above a speed threshold.** Rig: solo grass/day expert, full forced throttle + constant 0.12
turn, BT_FORCE_SEEK, 150 s/run (`scratchpad/night16/myo173.sh` + `myo173b.sh`, digest
`digest173.py`, logs `content/m173_*.log`). Streaming receipts on every chassis matched the
authored data exactly ([heat-link] Myomers sinkIdx=8→Condenser5 k=1.9e5 m=2.5e5; [spec]
hsCount 18/14/28/13/15/90t...; C5 mScale=3 flowScale=0.1667 balanced). Matrix (peak v /
steady v u/s, time to degT 1000, equilibrium T, C5 end):
- vulture seek-1: 24.5/21.1, never, **eq 423**, C5 333 — gears 1-3 are harmless (ratio floors 1).
- vulture seek-4: 56.9/31.9, **13.9 s**, **eq 1801**, C5 1410 (loop-load bar full-scale ~15-20 s).
- madcat seek-4: 56.8/28.4, 12.1 s, eq 1820, C5 1420. avatar seek-4 (HUMANOID, same 143-kph
speed class in the port): 56.2/29.5, 14.3 s, eq 1819, C5 1424 — **identical cook**.
- thor seek-4: 34.6/34.3, 79.9 s, 1311 still climbing; sunder (90 t): 34.6/34.0, 49.4 s, 1592
climbing — the port's slow (87-kph-class) chassis merely take longer.
- STRAIGHT-line control (no turn): eq 1802, |a|≈20 — same as turning, so the accel term is
GAIT-SURGE noise in the velocity ring, not commanded motion (see residual below).
- **Valve boost, the authored counter-play** (one MoveValve press on Condenser5, detent 1→5 =
share 0.5): myomers still governor-pinned ~1715 but **sustained drive 0.68 vs 0.54 balanced
(v 39-41 vs ~32) and C5 968 vs 1410** — boost buys back speed, not myomer temp. The run's
accidental map-edge stop measured the standstill shed: 1723→586 in ~35 s (10/s) — "heat
only sheds near standstill" is the fixed-capacity chain being honest (slope +0.02/s while
cruising).
**Mechanics of the thermostat**: T rises past degT → AvailableOutput derates → v falls →
m·v² generation falls → equilibrium lands ~1700-1820, just UNDER failT 2000, on EVERY chassis
fast enough to out-run the loop — better cooling raises the sustained SPEED at the same
pinned T. Steady seek-4 cruising never freezes (failT) solo; the field freezes need adders
(damage dmgGain ≤2x, combat weapon heat, respawn transients, a GenD trip on the shared loop).
**Manual cross-check settles the speed residual in favor of AUTHENTIC** [T1 print, re-read
via fitz p24/25]: MadCat prints **175 N / 220 SC**, Vulture **175 N**, Thor/Loki 143/182 —
the machine's big chicken walkers were FASTER than the port's measured 143 N / 205 SC (thor
port 87/124 is far under its print), so authored m·v² generation on the pod was ≥ what these
benches produced; the phenomenon (manual p21 warns of it explicitly) is authored. The port's
per-chassis top-speed shortfalls remain a LOCOMOTION-lane item but cannot rescue a "port too
hot" theory — correcting them makes it hotter.
**Verdict: AUTHENTIC mechanism + authored balance [T2]; ONE bounded port-side severity
residual [T3]** — the accel term's |a| operand (15-sample velocity-ring derivative) is
frame-cadence-sensitive: at ~59 fps a straight flat cruise reads |a|≈14-20 (thor/sunder's
smoother gait ≈4) and the accel term carries 50-65% of steady seek-4 generation; the same
gait bob sampled through the pod's 28 Hz ring would read ~2-3x smaller, so the pod's
equilibrium may have sat ~1200-1500 (shallow governor, near-full supercharge speed held)
instead of the port's ~1800 (deep governor, speed sags to ~0.54). Same phenomenon, softer
edge — this is the gap that would reconcile Oracle's "ran 182 kph sustained" pod memory.
If field calibration is ever wanted, the knob is the |a| feed's cadence (sample the ring at
28 Hz), NOT the formula constants (byte-exact, #137). Also note the CLIMB term is inert in
the port (g=0, EnvironmentZone unwired) — the pod added heat on slopes that we do not.
+44
View File
@@ -111,6 +111,50 @@ WE NEED YOUR MEMORY
>
>
-----------------------------------------------------------------------------
2B. SEEK-4 ON THE HEAVY WALKERS (VULTURE / MADCAT / THOR / LOKI)
-----------------------------------------------------------------------------
THE ORIGINAL'S BEHAVIOR (audited to the byte this week)
- Drive heat scales with weight times speed squared, and no amount
of running ever cools you -- there is no airflow cooling anywhere
in this machine. The fast-heavy Clan walkers pay the most.
- Gears 1 through 3 make IDENTICAL heat: seek-3 is free speed.
Seek-4 roughly doubles drive heat AND raises your top speed --
a sprint gear. Cruising it on a heavy walker crosses myomer
degradation in about 14 seconds and the governor drags you to a
crawl. A same-weight humanoid at the same speed cooks the same:
it is physics, not a chicken-walker curse.
- The machine gave you the tool: BOOST COOLANT LOOP 5 (Generator D /
Myomers). One press visibly buys your speed back; a full boost
sustains seek-4 on a Vulture indefinitely.
- THE TRAP: one press past maximum WRAPS THE VALVE CLOSED. If you
ever boosted a loop and it cooked anyway -- you probably hit the
wrap. Two presses, never three.
- Standing still sheds heat fast (~10 degrees a second).
OUR PORT TODAY
All of the above, byte-faithful -- and our walkers actually run a
little SLOWER than the machine's printed speeds, so if anything the
pods cooked slightly faster than we do. One open sliver: our
governor may bite a touch harder than you remember (a frame-timing
nuance under study), which the question below settles.
CHANGING IN THE NEXT BUILD
Nothing mechanical.
WE NEED YOUR MEMORY
- At seek-4 on a Vulture or MadCat -- balanced valves, flat ground
-- did your speed sag within ~15 seconds, or could you hold
supercharge speed sustained?
- Did the loop-5 valve boost trick live in era pilot lore, or are
we rediscovering it?
YOUR NOTES (callsign first, one entry per line):
>
>
>
-----------------------------------------------------------------------------
3. PPC AND ER PPC
-----------------------------------------------------------------------------