Engineering notes on capturing and replaying deployed software evidence.https://kodecapture.com/en-ushttps://kodecapture.com/journal/a-timeout-does-not-prove-the-browser-is-gone/https://kodecapture.com/journal/a-timeout-does-not-prove-the-browser-is-gone/Why cleanup confirmation is part of the result rather than a best-effort afterthought.Tue, 29 Sep 2026 00:00:00 GMThttps://kodecapture.com/journal/a-fresh-browser-is-part-of-the-capture-input/https://kodecapture.com/journal/a-fresh-browser-is-part-of-the-capture-input/Why executable identity, owned profiles, and control transport belong in acquisition evidence.Sat, 26 Sep 2026 00:00:00 GMThttps://kodecapture.com/journal/a-request-file-should-never-be-selected-by-accident/https://kodecapture.com/journal/a-request-file-should-never-be-selected-by-accident/Why KodeCapture uses explicit acquisition intent instead of ambient working-directory discovery.Wed, 23 Sep 2026 00:00:00 GMThttps://kodecapture.com/journal/serve-is-for-browsing-replay-is-for-qualification/https://kodecapture.com/journal/serve-is-for-browsing-replay-is-for-qualification/Two useful commands with different promises, evidence, and browser ownership.Sun, 20 Sep 2026 00:00:00 GMThttps://kodecapture.com/journal/capture-is-an-evidence-boundary/https://kodecapture.com/journal/capture-is-an-evidence-boundary/A useful software capture records which bytes, routes, requests, states, and policies produced the evidence—and which parts of the application remained unseen.Wed, 12 Aug 2026 00:00:00 GMThttps://kodecapture.com/journal/capturing-interaction-without-clicking-blindly/https://kodecapture.com/journal/capturing-interaction-without-clicking-blindly/Exploration needs budgets, risk policy, structural state measurement, and a terminal disposition for every candidate action.Wed, 12 Aug 2026 00:00:00 GMThttps://kodecapture.com/journal/network-replay-is-protocol-work/https://kodecapture.com/journal/network-replay-is-protocol-work/Fetch, XHR, GraphQL, and WebSocket evidence have different matching, ordering, and authority requirements. Recording bodies alone is not enough.Wed, 12 Aug 2026 00:00:00 GMThttps://kodecapture.com/journal/offline-interaction-evidence-without-egress/https://kodecapture.com/journal/offline-interaction-evidence-without-egress/A rehydrated workspace can support interaction evidence only when it runs sealed bytes, blocks external requests, repeats the flow cold, and binds every promoted artifact.Wed, 12 Aug 2026 00:00:00 GMThttps://kodecapture.com/journal/refresh-donor-without-overwriting-candidate/https://kodecapture.com/journal/refresh-donor-without-overwriting-candidate/When production changes during recovery, capture evidence should advance transactionally while the editable candidate remains under engineering ownership.Wed, 12 Aug 2026 00:00:00 GMThttps://kodecapture.com/journal/route-coverage-is-bounded/https://kodecapture.com/journal/route-coverage-is-bounded/Multi-page capture needs normalized queues, origin and path boundaries, depth and page budgets, and diagnostics for every route that was skipped or failed.Wed, 12 Aug 2026 00:00:00 GMThttps://kodecapture.com/journal/a-screenshot-is-not-a-replay/https://kodecapture.com/journal/a-screenshot-is-not-a-replay/Pixels can show that one frame looked right. Replay evidence must also preserve the route, resources, interactions, runtime state, and authority that produced it.Wed, 12 Aug 2026 00:00:00 GMThttps://kodecapture.com/journal/sealed-bytes-and-capture-authority/https://kodecapture.com/journal/sealed-bytes-and-capture-authority/Replay evidence should be bound to exact donor bytes, response inventories, generated source, and mutation plans so later tooling cannot silently change what was observed.Wed, 12 Aug 2026 00:00:00 GMT