Temporary Proof Modules Should Not Become Permanent Architecture
How scratch-only verification work can support a change without leaking scaffolding into the deliverable.
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.
An intermediate module can be useful for proving a bounded transformation. That does not mean the module belongs in the final recovered project.
Kalu’s package-externalization architecture includes strict-terminal proof-module composition. The idea is to connect a carve, a proof step, and an externalization through exact intermediate states while keeping scratch-only scaffolding out of the net deliverable.
Temporary structure has a specific job
Consider a synthetic operation that isolates a dependency region into a temporary module so that a later stage can verify it. The temporary file helps establish a relationship between source bytes and a proposed replacement. It is not automatically a maintainability improvement the application should keep.
If the final candidate retains every intermediate wrapper, recovery can leave behind a second architecture made of tool scaffolding. The project may build while becoming harder for a maintainer to understand.
Bind the whole chain
The current composer requires exact preimage and postimage relationships across intermediate operations and complete terminal member accounting. It can remove net scratch-only create-and-delete chains from the fused operation, but it cannot pretend the intermediate proof never needed authentication.
The remaining operations are bound to the certified producer plan before the durable transaction applies them. This keeps the temporary proof path connected to the actual final bytes rather than allowing an attractive final diff to stand in for the missing chain.
Composition is not a passing gate factory
The composer does not manufacture passing measurements. Gate owners remain responsible for producing the evidence appropriate to their subjects, and certification must resolve that evidence independently. A temporary proof module is a technique within the chain, not a shortcut around it.
The source-level mechanism should also not be mistaken for complete integration of every legacy hashed-chunk path. Some owners retain explicit blockers until the required product authority is available.
For a recovery handoff, ask whether each remaining file serves the application or merely served the tool. Useful proof scaffolding can be temporary without being unaccountable. The goal is a final candidate whose architecture reflects the maintenance target, with enough evidence to explain how the temporary work led there.