Do Not Replace Half a Singleton Family
Why coordinated package identity matters more than a successful individual import rewrite.
Scope: Engineering or methodology note based on a September 17, 2026 snapshot. Source-level behavior is not a public availability or universal compatibility claim. Any scenarios are illustrative, not customer outcomes.
Some dependency relationships are sensitive to shared identity. Replacing one consumer while leaving another attached to an inline implementation can create two versions of something the application expects to be one.
That is why Kalu’s package-externalization planning treats singleton and family conversion membership as an explicit universe. A partially converted singleton family is not a valid plan shape.
A local improvement can create a global split
Imagine a synthetic application where two consumers share a registry or constructor identity. One consumer is rewritten to import an installed package, while the other retains a bundled copy. Both files may parse. The build may succeed. Their relationship can still be wrong.
The defect does not live in either import statement alone. It lives in the partial conversion. A plan needs to account for all relevant family members and their exact provenance before a later stage can authorize the change.
Bind every identity that can go stale
The current externalization plan binds package, lock, installed distribution, and candidate provenance. A change to those inputs can make the plan stale. Root specifiers, export keys, subpaths, and rewrite targets need to agree rather than be repaired informally during application.
The source also refuses mixed exact and versionless cohorts atomically. That avoids letting a strong identity claim for one member disguise a weaker claim for another member in the same conversion.
Build success is not the terminal gate
Externalization certification requires independently resolved evidence appropriate to the plan, including the relevant coverage and residue obligations. Caller-declared passing statuses cannot manufacture a certificate. Applying the result is another boundary with exact bytes and transaction authority.
This article describes a source-level design and its bounded implementations. It is not a statement that every singleton-sensitive package or every legacy seed path is currently integrated. The actual product path must supply the required authority; an old planned row or a receipt-shaped string is not enough.
The practical question is whether the tool can explain the complete identity family it intends to convert. If it can only show one attractive import diff, the most important part of the operation may still be missing.
Explore an authorized recovery assessment. Begin with a non-confidential description; do not send credentials or private source material in the first message.