# Exercise 2 — report the work that actually happened

**Outcome:** a short weekly review with traceable status and suggested next actions. This is a fictional practice week; calendar dates are intentionally absent.

## Input and prompt

N1 Monday: Client A login fix closed after a test. N2 Tuesday: invoice checked and sent, complete. N3 Wednesday: same Client A login issue reproduced; reopened. N4 Thursday: Client B login issue closed after testing. N5 Friday: requested moving the demo; time not agreed; calendar unchanged. N6 Friday: new logo idea, no commitment.

Use `$weekly-review` or `/weekly-review`: “Review these notes. Separate completed work, current open work, and suggested next actions. Keep source IDs. No agreed priority order exists. Do not update anything.”

## Worked output

Completed: invoice checked and sent (N2); Client B login issue closed after testing (N4).

Open: Client A issue was closed (N1), then reproduced and reopened (N3). Demo move remains unconfirmed and the calendar unchanged (N5). The logo is an idea, not a committed task (N6).

Suggested next actions: resolve the demo timing to prevent conflicting expectations (N5); investigate and retest Client A's issue (N3); leave the logo idea uncommitted unless a priority decision is made (N6). This order is a proposal, not an agreed deadline or assignment.

The review reports what the notes say. It does not establish that a real invoice was sent or that an external calendar was checked.

## Failure and repair

Failure: “Both login bugs fixed; demo moved to next Friday.” This collapses clients, ignores the reopened issue and invents the new meeting time. Repair by preserving task identity and using the latest applicable status for each item. Do not map weekday-only notes onto today's calendar.

## Changed input

Add N7: Client A bug retested and closed after a second fix. N8: demo move accepted, but calendar update still pending. Produce the revised current status.

Answer check: Client A now complete as reported in N7, with reopen/fix history retained if useful. The new demo time is agreed but still not supplied in these notes, and the calendar update is pending. Neither the model nor the notes establish the actual timestamp or a calendar write. Client B remains distinct and closed.

## Complete when

Every completion has supporting evidence, later updates supersede the right earlier task, unknowns stay unknown and proposed next actions are labeled. If the host invents dates, rerun with the explicit condition “retain weekday labels; no calendar dates are supplied,” then compare the repair. If task identity is ambiguous, ask the one question needed to avoid merging unrelated work.