When the call changes, check its approval again

An agent gets permission to write a file, then changes the path before sending the call. It needs approval for the call it actually sends.

Now take a different case: the approved write completes, and someone changes the file later. That later change needs its own observation. It should not erase the earlier matching result.

Read the shared case table. It follows giskard09’s selected execution-join contract and keeps the proposed later-state outcome separate from its existing digest checks.

Bring a reader, the producer’s vectors, or a retained file-effect run to the Lab thread. Another project can run the same cases and compare outcomes directly with you. We maintain the case table and credit the case, code and runs separately.

The SQL example gives you a runnable comparison of a matching recorded commit and a later state difference. The execution-join table is a proposed experiment; its native verifier run is a separate contribution.