# Parent comparison: image 073

Parent: /root, local task 01a0e067-c27c-77f2-a3f9-ec52a44b62cf. Fresh describer: /root/blind_073, gpt-6-luna high, forked with no conversation context. Its only evidence input was this image. Parent read the completed description and verified the image checksum.

[Actual screenshot](../inputs/073.png) · [Independent description](../descriptions/073.md)

Variant B. Captured action: After interleaved proposal and lead GUI saves and both reloads. URL: https://kertujitok-proposal-b-20260927.clientsflowdigital.workers.dev/panel/proposals/?proposal=p_eeca30be616cc99d56853b41a59a943ec89632e7a1b6af5598bef35c26976eef. Screenshot SHA256: `9ffac9830c346c1c0608530e80098508c902428c97695ef77fdc284aad09cb89`.

- C02: When the Test Garden lead and proposal are edited and saved in variant A, then those changes survive a reload in A while the same starting records in variant B remain unchanged. When the edits are repeated in B and interleaved with A saves, then each variant retains its own distinct saved values and never overwrites the other.

**Parent comparison:** The independent description sees B-specific proposal address 2 at saved version 3 with the same 374,500 Ft starting total. Together with A image 072 and the interleaved A1/B1/A2/B2 save and reload receipts, this supports independent persistence. The screenshot does not itself prove isolation, so final API field readbacks and each opposite-origin reload remain part of C02 proof.

[Completed GUI journeys and exact behavioral evidence](../../deployed-gui/scenario-matrix.md). Full criterion acceptance also requires the other applicable states and nonvisual checks. A screenshot alone does not prove persistence, timing, arithmetic or downloaded bytes.