What this method reports
| Finding | Meaning |
|---|---|
| Boundary edge | An edge is used by one triangle under the implemented incidence rule. |
| Over-shared edge | More than two triangles use an edge; the report labels this non-manifold. |
| Component count | Vertex-connected groups within each placed build item, summed across items; not a count of defective parts. |
| Winding conflict | Two incident triangles follow the shared edge in the same direction. This does not establish the intended outside. |
| Completed with no listed findings | Supported checks completed without those findings; untested properties remain unresolved. |
Supported component and build transforms and source-unit conversion are applied before each build item is inspected independently. Exact endpoint coordinates define edges; there is no distance-tolerance welding. Invalid-coordinate and degenerate faces do not contribute to edge incidence; duplicate faces do. Components connect through any shared vertex coordinate. The displayed counts aggregate placed-item results, without per-resource localisation.
Edge incidence is one topology screen. A point-only contact or crossing surface can require additional inspection even when no over-shared edge is reported. Several intended closed parts should not be fused solely to make a component count smaller. This method does not run spatial intersection checks.
Choose the next investigation
Use boundary interpretation for exposed edges, local triangle cleanup for an understood redundant-face removal, and the resource versus placement guide for uncertain joins. A resource may be reused by several build items; changing its triangles differs from removing a placement. Keep the original and verify the saved package in the receiving slicer.