Record placement reference failures and port-clearance requirements

2026-09-24 20:26:23 -07:00
parent fc5c22c903
commit 2850b915d6
10 changed files with 3185 additions and 0 deletions
@@ -511,3 +511,23 @@ experiments and stop tuning this corpus. Reconsider adoption only with meaningfu
 named trace-task improvements, no newly ambiguous task, and appropriate runtime
 evidence. This is a branch-specific decision, not a completed Arrange feature or
 integrated release; the linked record retains rejected alternatives and limits.
+
+
+## Placement must respect derived ports and mandatory exits — 2026-09-25
+
+Branch-specific issue32 research, not an integrated release. The bounded
+[placement comparison](experiments/connection-layout-reference-20260925/results.md)
+shows that a node/label layout followed by independent port selection and routing
+is not a faithful transfer of a port-constrained engine result. Automatic ports
+change sides/slots after positions move even though authored anchors stay exact.
+The sparse reference's20-unit gap cannot contain the released router's18-unit
+port lead plus12-unit obstacle clearance. The sole endpoint pair is rejected
+before path search; increasing search work would not repair that placement.
+
+Keep both candidates experimental. A future candidate needs explicit final-port
+and mandatory-lead compatibility checks, compound/undirected semantics, and the
+existing preservation/native trace gates. Raw engine paths avoiding uninflated
+node interiors do not prove compatibility with our inflated obstacles and leads.
+Do not silently shorten those leads, move authored anchors, or persist external
+generated bends to make a comparison pass. Revisit engine integration only with
+a faithful geometry interface and observed usability benefit.