Capture Budgets Are Part of the Meaning of Complete

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 cannot observe an unlimited application for an unlimited time. It needs a declared boundary around the journey and the resources used to observe it.

That makes budgets part of the evidence contract, not merely performance tuning. A result that exhausted a required budget should not be described as complete simply because the page loaded and some useful files were saved.

A limit can change the conclusion

Consider a synthetic page whose required response arrives after the capture has exhausted its admitted body or request budget. The earlier observations may still be useful. They do not establish that the full declared journey was acquired.

The same principle applies to a deadline or an unreached checkpoint. A bounded operation should preserve the evidence it obtained while making the missing portion explicit. Partial is a meaningful result, not a failed attempt at looking complete.

The profile belongs with the report

Kalu’s capture and replay sources use explicit resource profiles and bounds. The exact values are implementation and policy details that need review for the product path; they should not be presented as universal performance benchmarks.

A buyer needs to know what was admitted and whether any required limit was reached. A large byte count is not automatically a better capture, just as a small one is not automatically incomplete. The declared journey determines which observations matter.

More time is not always the right fix

Raising a limit may be appropriate after investigation. It can also hide an unbounded or misunderstood behavior. The next step should identify whether the application requires broader support, a more precise journey, or a genuinely larger admitted budget.

The current KodeCapture surface remains an installed-product candidate with a narrow supported floor. These budget mechanisms do not imply support for every realtime, worker, or storage behavior a browser can expose.

For engineers, read “complete” as a statement about a declared request under declared limits. That is a much more useful claim than “we collected a lot.” A bounded product becomes trustworthy when it makes the boundary visible before someone mistakes a partial observation for the entire application.