Update the tracker after an amendment and invoice receipt

G06 · v0.1.0 · Optional fictional exercise. Complete the baseline before opening the new packet.

New facts

Open the changed-facts pack. C06 is a second signed amendment dated 1 July 2026. C07 records a valid invoice receipt on 2 July. Prepare an update as at 3 July 2026, 17:00 UTC+03:00, preserving your baseline as at 30 June.

What to produce

Update the affected existing entries, add any new duty with a new ID and reconcile the date-check sheet. Log every changed field, its previous/new value, source and reason. Inspect reminder proposals as well as dates. Do not invent a payment-reminder lead time, completion record or internal owner.

Check whether the new amendment applies to the already-recorded June report or only future periods. Decide whether it changes the initial term, renewal rule or unresolved transition trigger. Show unchanged entries as unchanged when the sources justify that.

Handover

Give the reviewer the original and updated register, source set, date checks and change log. Explain which dates are stated, which are calculated examples and which remain blank. No live calendar events, notices, payments or external messages are authorised.

The main guide and field guide describe the method. Expected answers and scoring remain in the separate reviewer pack.