A claimed fix is not a closed issue.
Discipline teams correct their source models. CNE verifies the change, reruns the relevant tests and confirms whether the conflict is genuinely resolved.
Corrections can move a clash instead of solving it.
Model correction belongs with the discipline responsible for the source design. Once an updated file is submitted, CNE checks the revision, rebuilds the federation and re-tests the affected interface against the same matrix and tolerance that identified the issue.
A visual check is not enough. Moving a duct clear of one beam may push it into another service, reduce access to a valve or violate a clearance rule elsewhere along the route. Without regression testing, the team can close one issue while creating several new ones.
We distinguish corrected, partially resolved, accepted and still-open conditions. The resulting closure record shows which tests passed, which issues returned and whether the coordination baseline is ready for the agreed stage sign-off.
Proof that the correction holds
Updated discipline files are checked for revision, coordinates and completeness before replacing the previous federation inputs.
The changed geometry is compared with the assigned action and decision record to confirm that the intended response was modelled.
Relevant hard, clearance and workflow rules are rerun using the original test logic, tolerances and element relationships.
Adjacent systems and wider rulesets are checked to detect new conflicts introduced by the correction.
Verified items are closed, incomplete fixes are returned with evidence and accepted exceptions retain their approval record.
CNE hands over the final issue register, residual clash list, test summary and model baseline for the agreed coordination stage.
Closure requires evidence.
We verify fixes against the same matrix and tolerances, preventing subjective closure based on a favourable camera angle.
Regression checks examine the consequences of each change beyond the single issue that prompted it.
Our handover states the tested model revisions, remaining exceptions and coordination stage covered by the closure decision.
Finish the cycle with verified models.
Send us the corrected discipline files and current issue register. We will re-test the changes, expose regressions and document the route to sign-off.