An Intact Capture Can Still Be Incomplete

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 capture can be internally intact while missing evidence required by the intended journey. Integrity and completeness are different properties, and a product should not let a successful seal check stand in for both.

KodeCapture’s source separates validation of capture authority from the broader question of what was actually observed. A sealed artifact can preserve an incomplete acquisition faithfully.

Integrity asks whether the record changed

A seal and its associated identities help establish that the admitted record and bytes are the ones being inspected. That is essential for later recovery and comparison. Without it, the reference could drift while retaining the same informal name.

But a seal cannot invent an uncaptured response, an unreached interaction, or a required checkpoint that never settled. It can authenticate the record of those limitations just as accurately as it authenticates a successful observation.

Completeness belongs to the declared request

Imagine a synthetic two-step journey where boot succeeds and the first interaction never reaches its required state. The capture may contain valid boot evidence. It should not become complete for the whole request merely because the files and metadata are internally consistent.

The current capability floor preserves partial outcomes for required unavailable bodies, unreached journeys, and truncation. Those conditions need to remain visible even when a supported capability was used correctly for the portion that completed.

Downstream tools need both answers

A recovery step may be able to use some admitted evidence from a partial capture. That does not permit it to describe the missing behavior as observed. The downstream claim must remain no broader than the evidence it consumes.

Likewise, a user should not infer that validation launches a browser or requalifies the journey. The current validation path is a bounded analysis of capture authority with independent verification.

This article describes the September source’s evidence boundary, not a guarantee of complete acquisition for arbitrary applications.

For an evaluator, ask two separate questions: is this the intact record we intended to inspect, and did the record satisfy the declared acquisition request? Both matter. Combining them into one green label makes the artifact easier to market and harder to use responsibly.

Discuss early-access fit. Begin with a non-confidential description; do not send credentials or private source material in the first message.