What problem does it solve? Migrating a Divalto ERP customer-specific downgrade layer onto a new Service Pack can silently erase overWrite overloads when compilation order is wrong, and missing standard sources make it impossible to decide what to keep or drop using a simple text diff. ## Core Features & Use Cases - Build Order Guidance: Enforces the golden rule of compiling standard bases first and overWrite overloads last, with a two-pass workaround for undeclared .dhps inter-project dependencies. - Overload Integrity Verification: Runs check_overwrite_order.py on .dhop object pairs or whole objets/ directories to detect date inversions and lost overload symbols after a rebase. - Downgrade Source Arbitration: Cross-references three signals (textual diff, compiled object existence, dictionary/RecordSQL coupling) to classify each source as keep, rebase, or drop. - Use Case: After rebasing on a new Service Pack, a screen reverts to standard behavior; scan objets/ to find which overWrite overload was silently erased and recompile it last. ## Quick Start Verify that my overWrite overload survived the Service Pack rebase by checking the base and overlay .dhop objects in the objets folder.
