12. Three practical cases

A small reversible correction

The owner asks for a clearer message in the App. The agent finds the actual interface and its requirement, changes the text and exercises the affected state. It checks whether wording could misrepresent a permission or data operation. If not, ordinary proportionate verification is sufficient. It does not create a graph, run record or new management assignment.

A consequential numerical change

The owner authorizes a bounded numerical repair. The owner of that work reads the current Design conditions and queries affected consumers. It checks the independent numerical reference and keeps parallel writers disjoint. An independent reviewer examines the substantive change. The agent runs affected checks, updates any changed condition in its current source, and integrates the reviewed candidate under the grant. A changed accepted tolerance goes to the owner instead of being silently adopted.

Recovery after interruption

A check was started, but its final response was lost. The next session inspects the actual process and result location before running it again. It checks the working tree and current PR head. Valid completed work remains usable. A short recovery note is replaced with the current situation if one is still needed; no new handoff chain is created.