<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>KodeCapture Journal</title><description>Engineering notes on capturing and replaying deployed software evidence.</description><link>https://kodecapture.com/</link><language>en-us</language><item><title>Capture Is an Evidence Boundary, Not a Download Button</title><link>https://kodecapture.com/journal/capture-is-an-evidence-boundary/</link><guid isPermaLink="true">https://kodecapture.com/journal/capture-is-an-evidence-boundary/</guid><description>A useful software capture records which bytes, routes, requests, states, and policies produced the evidence—and which parts of the application remained unseen.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Capturing Interaction Without Clicking Blindly</title><link>https://kodecapture.com/journal/capturing-interaction-without-clicking-blindly/</link><guid isPermaLink="true">https://kodecapture.com/journal/capturing-interaction-without-clicking-blindly/</guid><description>Exploration needs budgets, risk policy, structural state measurement, and a terminal disposition for every candidate action.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Network Replay Is Protocol Work</title><link>https://kodecapture.com/journal/network-replay-is-protocol-work/</link><guid isPermaLink="true">https://kodecapture.com/journal/network-replay-is-protocol-work/</guid><description>Fetch, XHR, GraphQL, and WebSocket evidence have different matching, ordering, and authority requirements. Recording bodies alone is not enough.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Proving Offline Interaction Evidence Without Network Egress</title><link>https://kodecapture.com/journal/offline-interaction-evidence-without-egress/</link><guid isPermaLink="true">https://kodecapture.com/journal/offline-interaction-evidence-without-egress/</guid><description>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.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Refresh the Donor Without Overwriting the Candidate</title><link>https://kodecapture.com/journal/refresh-donor-without-overwriting-candidate/</link><guid isPermaLink="true">https://kodecapture.com/journal/refresh-donor-without-overwriting-candidate/</guid><description>When production changes during recovery, capture evidence should advance transactionally while the editable candidate remains under engineering ownership.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Route Coverage Is Bounded—and Should Say So</title><link>https://kodecapture.com/journal/route-coverage-is-bounded/</link><guid isPermaLink="true">https://kodecapture.com/journal/route-coverage-is-bounded/</guid><description>Multi-page capture needs normalized queues, origin and path boundaries, depth and page budgets, and diagnostics for every route that was skipped or failed.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item><item><title>A Screenshot Is Not a Replay</title><link>https://kodecapture.com/journal/a-screenshot-is-not-a-replay/</link><guid isPermaLink="true">https://kodecapture.com/journal/a-screenshot-is-not-a-replay/</guid><description>Pixels can show that one frame looked right. Replay evidence must also preserve the route, resources, interactions, runtime state, and authority that produced it.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item><item><title>Sealed Bytes and Authenticated Capture Authority</title><link>https://kodecapture.com/journal/sealed-bytes-and-capture-authority/</link><guid isPermaLink="true">https://kodecapture.com/journal/sealed-bytes-and-capture-authority/</guid><description>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.</description><pubDate>Wed, 12 Aug 2026 00:00:00 GMT</pubDate></item></channel></rss>