Part F: one fault, through the ledger

You see a fault through to a correction that someone other than the fixer has rechecked against the original criterion.

Principles in play: Evaluate corrections.TRACEEvaluate corrections

Needs: nothing beyond the hour, and both of you. The fault is the work you returned at minutes 30 to 45, if any; otherwise B raises the inherited calculation, which averages the yearly percentages, and A the inherited reference with no source at its DOI.

What you do

1. Raise it. If you returned the work, your return already opened the row:

   Say to your agent

   Show me the row my return opened.

   If the fault is inherited:

   Say to your agent

   This line is wrong: (quote it). Open a defect row for it in my name.

   Read the row, which reads open, then say finalize.

2. Your partner fixes it, as the owner of the file, after pressing Sync Changes:

   Say to your agent

   Fix this fault and mark the row fixed in my name.

3. Recheck it. Press Sync Changes, then:

   Say to your agent

   Recheck the fix against the original criterion, with my own evidence.

   B recomputes the share from the two count columns; A looks the reference up at its DOI.

4. Read the recheck account field by field, with you as checker and your partner as implementer. If it says what you did:

   Say to your agent

   Run it.

   The row reads verified, or says why it did not verify.

5. Open ai/defects.jsonl: the row carries the three steps and the names on each.

Ask your agent

• Who opened the row, who fixed it, and who rechecked it? Is the checker the fixer?
• What did the recheck compare, and what did it not cover? Is the row verified or closed, and what is the difference?

What you can say now

A fault went into the ledger under a name, its owner fixed it, and the person who raised it rechecked the fix against the original criterion with their own evidence: that is E, evaluate corrections. If the row reads verified, a targeted recheck supports the correction; closed would say only that a later review did not raise the finding again.