# Two complete authored wrong plans

These counterexamples were written for this fictional exercise. They are not captured model answers, observed user mistakes or a measured error rate. All clock times are 14 May 2030, UTC. Each row's listed minutes equal its own end minus start; the errors concern overlaps, task constraints and unsupported claims.

## WRONG-V1

Incorrect claim: “All seven tasks fit inside the day; the plan is ready.”

| Block ID | Start (UTC) | End (UTC) | Minutes | Entry |
| --- | --- | --- | ---: | --- |
| T02 | 09:00 | 10:15 | 75 | Review note, wrongly before its prerequisite |
| T01 | 09:45 | 10:30 | 45 | Inspect sample dataset |
| F01 | 10:00 | 10:30 | 30 | Team coordination meeting |
| T03 | 10:30 | 12:00 | 90 | Handoff checklist |
| F02 | 12:00 | 12:45 | 45 | Lunch |
| T04 | 12:45 | 13:45 | 60 | Tracker reconciliation |
| T05 | 13:45 | 15:15 | 90 | FAQ draft, wrongly during fixed time |
| F03 | 14:30 | 15:00 | 30 | Project review meeting |
| F04 | 15:00 | 15:15 | 15 | Break |
| T06 | 15:15 | 15:45 | 30 | Reference snippets |
| T07 | 15:45 | 16:45 | 60 | Workshop outline |
| G01 | 16:45 | 17:00 | 15 | Unallocated |

Wrong task accounting: T01 45, T02 75, T03 90, T04 60, T05 90, T06 30, T07 60 minutes; every task is presented as scheduled and none unscheduled. That is 450 task minutes against only 360 available. T01 overlaps T02 and F01; T02 starts before T01 finishes; T05 overlaps F03 and F04. Keeping correct row durations does not make the combined day feasible.

## WRONG-V2

Incorrect claims: “The new meeting is included and everything still fits. Morning work before 13:00 is complete. T02 has its 75 minutes and T03 has its 90 minutes.” This update actually arrives at 08:45, so those completion claims have no basis.

| Block ID | Start (UTC) | End (UTC) | Minutes | Entry |
| --- | --- | --- | ---: | --- |
| T01 | 09:00 | 09:45 | 45 | Dataset inspection, wrongly marked complete |
| G01 | 09:45 | 10:00 | 15 | Unallocated |
| F01 | 10:00 | 10:30 | 30 | Team coordination meeting |
| T02 | 10:30 | 11:30 | 60 | Review note, compressed from 75 and wrongly marked complete |
| T03a | 11:30 | 12:00 | 30 | First checklist block, wrongly marked complete |
| F02 | 12:00 | 12:45 | 45 | Lunch |
| T04 | 12:45 | 13:45 | 60 | Tracker, overlapping the new fixed commitment |
| F05 | 13:00 | 14:00 | 60 | New equipment walkthrough |
| T03b | 14:00 | 14:30 | 30 | Second checklist block; total is only 60, not 90 |
| F03 | 14:30 | 15:00 | 30 | Project review meeting |
| F04 | 15:00 | 15:15 | 15 | Break |
| T05 | 15:15 | 16:45 | 90 | FAQ draft |
| T06 | 16:45 | 17:15 | 30 | Snippets, extending past work end and its deadline |

Wrong task accounting lists only T01 45, T02 60, T03 60, T04 60, T05 90 and T06 30 as scheduled. It silently drops T07's 60 minutes and supplies no unscheduled list. Allocated task minutes total 345, not the unchanged 450-minute demand. T02 loses 15 minutes, T03 loses 30, T04 conflicts with F05, and T06 runs 15 minutes outside the work window and beyond its 17:00 deadline. No task may be dropped, shortened or declared complete to conceal the shortfall.

## Repair both complete versions

Keep every original estimate and fixed block. Rebuild V1 and V2 from their actual inputs and Rowan's selection rule; do not merely slide the conflicting rows later. Restore T07 to both task inventories and restore the full estimates for T02 and T03. Mark every allocation as planned. Explicitly retain work that cannot fit. The [complete repair request](./complete-repair-request.en.txt) contains all inputs and both wrong versions; [the corrected plans](./plans.en.md) give full replacements, not isolated patches.