erik/acdream
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs: #341 live A/B — the user's slope run shows the bare-radius trigger would fire on 84% of grounded slope ticks

Browse source 
3,870 player resolves captured at Rithwic with ACDREAM_CAPTURE_RESOLVE.
Of 2,955 contact-seeded ticks the RETAINED trigger fired zero times —
the current push-out is inert in ordinary play — while retail's bare
trigger would have fired on 2,471 (84%), lifts 2-88 mm, p50 27 mm. The
body rests at r*N.z every grounded tick, so landing AD-66 alone would
engage the push on virtually every slope step and fight the foot
planting: the oscillation the original substitution was written against.

The exposed question sits upstream: our placement plants the sphere
vertically (perpendicular r*N.z); if retail's walkable contact rests
tangent (perpendicular r), retail's bare trigger is inert in retail
exactly as ours is here, and the trigger cannot be ported without the
placement geometry. That retail-side verification is now the apparatus
session's first task, and it also gives the harness flip a mechanical
suspect: settle-state order dependence, not physics.

Measured from the user's own two-minute run rather than argued — the
cheapest decisive instrument of the campaign so far.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-07 07:15:12 +02:00
parent addb5657c3
commit ca0fad1482
2 changed files with 4925 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

27
docs/ISSUES.md
View file

@ -183,6 +183,33 @@ conformance exact-value tests passed in the same clean-room). 0.0798 m =
outcomes are physically coherent stories — the problem is that the same
binaries told both.
### LIVE A/B, 2026-08-07 morning — the user's slope run settles the stakes
`341-slope-capture.jsonl`, 3,870 player resolves at Rithwic (landings on the
face, uphill holds, traversal, standing): of **2,955 contact-seeded ticks**,
the RETAINED trigger (`dist < r*N.z - eps`) fired **0** times — the current
push-out is completely inert in ordinary play — while retail's BARE trigger
(`dist < r - eps`) **would have fired on 2,471 (84%)**, with per-fire lifts of
2 mm to 88 mm (p50 27 mm). The body demonstrably rests at its natural
distance `r*N.z` every grounded slope tick, so the bare-radius port is not a
quiet conformance fix: it would engage on virtually every slope step and
fight whatever plants the feet back on the surface — the per-tick
oscillation the original substitution's author described ("fires spuriously
on every slope… flickered the Falling animation").
**The REAL question this exposes sits one level upstream:** our grounded
placement plants the sphere centre VERTICALLY above the surface (perpendicular
distance `r*N.z`), and if retail's walkable contact instead rests the sphere
TANGENT to the plane (perpendicular distance `r`), then retail's bare trigger
is inert in retail for the same reason ours is inert here — and porting the
trigger without the placement geometry imports a fight retail never has. That
retail-side resting geometry is UNVERIFIED either way and is now the first
task of the apparatus session (grep/decompile retail's walkable placement:
does step_down/find_walkable leave perpendicular-r or vertical-r?). It also
offers a mechanical suspect for the harness flip below: the two assert shapes
plausibly differ in what settle state the harness left (`r*N.z` vs `r`),
which is test-ORDER state, not physics.
**Hypotheses deliberately NOT chased at 04:00:** a property-read side effect
(reading `body.ContactPlane` between tick and assert — should be impossible);
xUnit execution-order/parallelism interacting with harness or engine state;