← Back to journal

Dry Run Means Planned, Not Externalized

How to read a direct externalization preview without overstating what happened.

Evidence basisKalu, Korpus, and frozen Ushman source/docs snapshot reviewed September 17, 2026; no new runtime qualification performed
DisclosureEngineering 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.
Published by Kalu KodeRequest a KodeBack assessment →

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.

A dry run is valuable because it can expose the intended operation before the candidate changes. It loses that value when its output is described as though the operation has already been applied.

KodeBack’s direct externalization path distinguishes planning from publication. A dry-run result is planned. It is not an externalized workspace, a committed transaction, or a passing post-change comparison.

Use the preview to inspect intent

An engineer can review the proposed package, selected bindings, consumer rewrites, and relevant evidence before committing to a mutation path. This is the point to notice a surprising ownership boundary, missing reference material, or a scope that does not match the maintenance objective.

A synthetic example makes the distinction clear. A plan may describe replacing a recognized constructor with a package import. Until the certified operation is applied and measured through its intended path, the live candidate still contains the original code.

Do not infer later evidence from a plausible plan

The plan does not prove that package preparation succeeded, that all independent gates passed, or that the current candidate still matches the expected starting bytes. Each of those questions can invalidate the next step even when the dry-run output looked sensible.

The current product source binds direct externalization to authenticated references and a controlled comparison path. An actual workspace publication needs the appropriate certificate and transaction evidence rather than an operator interpreting “planned” as a softer spelling of “done.”

Keep screenshots and captions honest

This is especially important in public demos. A terminal screenshot of a dry run should say dry run. A diagram of the resulting imports should be labeled proposed unless it is tied to an applied artifact. A preview of a potential improvement should not become a claim that the application has already been recovered.

The source-level direct path also should not be conflated with older integration paths that still have explicit blockers. The existence of one implemented route does not erase a refusal in another owner.

Dry runs make recovery easier to review because they create space between intent and action. Preserving that space in the report and in the marketing copy is part of the feature. Planned is a useful outcome. It does not need to impersonate publication to be worth showing.