docs: #341 decision — user directs porting the retail pair (tangent rest + bare trigger, one slice)
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
4885629fbd
commit
eec50bbd24
1 changed files with 7 additions and 5 deletions
|
|
@ -238,11 +238,13 @@ rests TANGENT to the slope. Two independent decompilers now agree. Consequences,
|
|||
under the bare trigger, a planted start lifts once — which of the two the
|
||||
harness settle leaves is plausibly order-dependent test state.
|
||||
|
||||
**Queued decision (user, no urgency): port the retail pair (feet float
|
||||
slightly on slopes, exactly like retail — a visible feel change gated by
|
||||
eyes) or keep our pair (planted feet, one register row covering placement +
|
||||
trigger together, AD-66 re-titled accordingly).** Retail-first says port; it
|
||||
is deliberately not done silently because the difference is visible.
|
||||
**DECIDED 2026-08-07 by the user: "port the retail pair."** Tangent resting
|
||||
placement + bare-radius trigger land TOGETHER as one slice (S4b), gated by
|
||||
the user's eyes on a slope. The slice must first establish WHERE our planted
|
||||
rest comes from (the live capture's r*N.z rest was measured on outdoor
|
||||
TERRAIN — the prime suspect is the outdoor ground placement rather than the
|
||||
ported BSP walkable solve, which should already be tangent if the port of
|
||||
@0x00538210 is faithful). AD-69's seam-frame correction rides along.
|
||||
|
||||
**Hypotheses deliberately NOT chased at 04:00:** a property-read side effect
|
||||
(reading `body.ContactPlane` between tick and assert — should be impossible);
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue