code wiki / collision

topic: collision

10 modules sharing the collision name family (derived from the tree's prefix discipline).

The 'collision' topic family in the Nishi sovereign ecosystem addresses issues arising from overlapping or conflicting code entities, ensuring system integrity and maintainability. Modules like nx_collision_aabb provide foundational collision detection, while nx_collision_harm identifies and mitigates harmful dormant code. nx_collision_plan orchestrates resolution strategies, guiding the careful merging of shadows to maintain coherence across the ecosystem.

auto-narrated by the local model from this topic's module headers; links verified against the wiki index.

narrated overview -- maintained by the narration lane, module links verified against this wiki.

moduledescriptionlinesfuncs
nx_collision_aabb.nxaxis-aligned bounding box collision (Q14).1536
nx_collision_aabb_test.nxsmoke for nx_collision_aabb.731
nx_collision_harm.nxIdentifies and triages harmful dormant code from benign coexisting duplicates in the Nishi ecosystem.1005
nx_collision_plan.nxthe RESOLUTION PROPOSER: mechanizes the careful merge method for each shadow1148
nx_collision_plan_gate.nx915
nx_collision_resolve_batch.nxresolve shadow collisions per the operator's rule: "the more performant and427
nx_collision_resolve_sovaudit.nxone-shot SOVEREIGN resolver for the nx_sovereignty_audit shadow collision393
nx_collision_retire_safe.nxRetires redundant runtime copies of RETIRE_A_SUBSET shadows safely and reversibly.683
nx_collision_watchdog.nxWMS-M3: the COLLISION / REGRESSION / FLOATER WATCHDOG.23912
nx_collision_watchdog_gate.nxWMS-M3 REFEREE: proves the collision/regression/floater WATCHDOG2387