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

docs: cancel Campaign S slice S3 — planned on a misreading of AP-84

Browse source 
The slice text claimed a door's collision stays where the shut door was.
AP-84's own row refutes the scenario: an open door is ETHEREAL (#150)
and bypasses collision entirely, so a door only ever collides in its
registered default pose — the approximation is behaviourally equivalent
for the entire known BSP-part weenie population, and the row's risk
column already carries the revisit trigger for animated non-ethereal
BSP movers if they ever appear.

The campaign's governing lesson says register rows are leads that must
be re-measured; the dual of that is that a CORRECT row must not be
'fixed'. The plan itself committed the reading failure this time. No
fix, no gate, no door row in the morning sitting.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Erik 2026-08-07 01:50:29 +02:00
parent 55b07f6a62
commit 4721838916
1 changed files with 14 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

26
docs/plans/2026-08-06-collision-fidelity-campaign.md
View file

@ -128,21 +128,23 @@ the DATs.
---
### S3 — Animated collision pose
### S3 — Animated collision pose — CANCELLED 2026-08-07 (the slice was planned on a misreading)
**Row:** AP-84. **Files:** `LiveEntityDefaultPoseResolver.cs`,
`LiveEntityCollisionBuilder.cs`, `ShadowShapeBuilder.cs` (`partPoseOverride`).
**Row:** AP-84 — which stays exactly as it is.
Server entities with a MotionTableId register their BSP part shapes at the
default style's first-cycle LowFrame pose and never update them; retail uses
the live `CPhysicsPart` pose. A door's collision therefore stays where the shut
door was.
This plan's original S3 text claimed "a door's collision stays where the shut
door was." **That scenario cannot occur, and AP-84's own row says why:** an
open door is ETHEREAL (#150) and bypasses collision entirely, so the only
pose a door ever collides in IS the registered default pose. The row's risk
column already carries the honest residual — "an entity whose server-driven
motion state materially moves a BSP-bearing part while NON-ethereal would
collide at the stale default pose (no known case)" — with the revisit
trigger written. The register was right; this plan's summary of it was
wrong, which is the same reading failure the campaign's own governing
lesson warns about, committed by the campaign plan itself.
**Why not folded into S1:** different files, different subsystem (animation, not
membership), and it needs a *visual* gate that S1 does not — you have to watch
a door open and then walk through the doorway.
**Gate:** live. Open a door, walk through, close it, walk into it.
No fix, no gate, no door row in the morning sitting. AP-84 remains an
active, deliberate approximation.
---