Record boundary ordering comparison and native review

2026-09-24 22:19:18 -07:00
parent 3e21c1bca2
commit 4fcb65c0d3
14 changed files with 1271 additions and 0 deletions
@@ -575,3 +575,24 @@ comparison should preserve coherent SCC ranks while using actual cross-boundary
 neighbors to order siblings. Treat label association separately from route
 sharing, preserve the full quality vector, and retain native tracing as a later
 acceptance gate. No global gap or routing-penalty sweep follows from this result.
+
+## Incoming boundary order is useful but not sufficient — 2026-09-25
+
+The [boundary-order comparison](experiments/boundary-order-20260925/results.md)
+at3e21c1bc preserves SCC blocks/ranks and orders same-rank child blocks using
+incoming external source centers. Dependency components provide deterministic
+propagation; cycles use one simultaneous snapshot. It fixes the declared
+simple two-container tracing witness (sharing164→0) and three-parent chain,
+while preserving all ten flat Projects/metrics exactly. All20 candidates pass
+independent full-Project conservation. Native saved-Project inspection confirms
+the simple trace improvement without establishing a native planner integration.
+
+Retain the mechanism experimentally. Folded workshop sharing726.5→1077.5,
+expanded crossing6→7, and anchored/local-SCC label intersections prevent
+unconditional adoption. Native anchored labels remain readable while their
+backgrounds interrupt the parent border: geometric collision counts require
+severity and ownership interpretation, not silent removal. Full member displacement
+must be checked in f64 before final f32 rounding; checking only a rounded delta
+misses large-origin errors. No further parameter sweep or release change is
+justified by this checkpoint. Production selection, label handling and integration
+remain open; the user requested a stop after publication.