Complete repair request — CAL1

Use only the complete fictional inputs and authored wrong versions below.
Return two COMPLETE corrected day plans, V1 before U1 and V2 after U1,
with every fixed block, task block and unallocated gap. Apply Rowan's
explicit priority/tie/placement rule without changing estimates or fixed
commitments. Show all seven tasks in each disposition table with scheduled
and unscheduled minutes; account for every input minute. Explain the
changed allocations and the remaining decisions, including tasks still
due today but not allocated. A lower-priority task may use an unsuitable
gap left by a higher-priority unsplittable task under the supplied rule.

For every row calculate end minus start; check pairwise intersections,
work-window bounds, exact fixed blocks, split limits, dependency order,
latest finishes, whole estimates and the complete task-ID set. Show
480-minute window minus fixed time, task demand, allocated task minutes,
unallocated minutes and unscheduled demand, for each version.

Nothing has been executed. Use planned/scheduled, never done/complete.
Do not infer morning completion from the 13:00 commitment. Do not change
priorities, book another day, shorten tasks or move fixed blocks to make
them fit. Do not use a calendar account, ICS, invitations or reminders.
This is a text work product; no model trial, time saving or completion
guarantee is requested. The wrong versions are authored teaching examples.
Replace each whole wrong plan, rather than returning only error notes.

----- COMPLETE ORIGINAL INPUT -----
# CAL1: the complete day-planning input

This is original fiction. Rowan is the fictional planner and sole worker; every task below belongs to Rowan. The tasks are already clarified. The durations are estimates Rowan explicitly accepts for this exercise, not measured completion times or promises. No work has started and no task is reported complete.

## Day and fixed commitments

- Plan date: **14 May 2030**. Every time in this packet is **UTC**.
- Work window: **14 May 2030, 09:00–17:00 UTC**, with no overtime.
- Both V1 and the later V2 are prepared **before work starts**. V1 is prepared at 08:30 UTC; the one change arrives at 08:45 UTC. These are fictional scenario times, not actual execution timestamps.
- One person can do only one activity at a time. Start is inclusive and end exclusive: adjacent blocks may share an endpoint.
- All starting source materials are available at 09:00. T02 still requires the exception list produced by T01; the only task dependency is T01 → T02. No travel, setup or waiting time is required beyond the estimates and fixed blocks explicitly supplied here. This simplified assumption belongs to the example; add those costs when they apply to your day.
- Do not move, shorten or use fixed meetings or breaks for tasks. Preserve every task and every estimate in both versions. Do not infer completion from a block's clock time.

| Fixed ID | Start (UTC) | End (UTC) | Minutes | Commitment |
| --- | --- | --- | ---: | --- |
| F01 | 10:00 | 10:30 | 30 | Team coordination meeting |
| F02 | 12:00 | 12:45 | 45 | Lunch, unavailable for work |
| F03 | 14:30 | 15:00 | 30 | Project review meeting |
| F04 | 15:00 | 15:15 | 15 | Break, unavailable for work |

## Every task and its accepted estimate

Every deadline is an inclusive latest finish, not an intended start. T07's next-day deadline does not authorize working outside today's window or invent a booking for tomorrow.

| Task ID | Defined work | Estimate (min) | Latest finish (UTC) | Splitting | Dependency | Priority |
| --- | --- | ---: | --- | --- | --- | ---: |
| T01 | Inspect the supplied sample dataset and note exceptions | 45 | 2030-05-14 11:00 | No: one continuous block | None | 1 |
| T02 | Draft the review note using T01's exception list | 75 | 2030-05-14 14:30 | No: one continuous block | T01 must finish first | 1 |
| T03 | Draft the handoff checklist | 90 | 2030-05-14 17:00 | Yes: one or two blocks, each at least 30 min | None | 2 |
| T04 | Reconcile the project tracker | 60 | 2030-05-14 17:00 | No: one continuous block | None | 2 |
| T05 | Prepare the FAQ draft | 90 | 2030-05-14 17:00 | No: one continuous block | None | 3 |
| T06 | Archive the reference snippets | 30 | 2030-05-14 17:00 | No: one continuous block | None | 3 |
| T07 | Sketch next week's workshop outline | 60 | 2030-05-15 12:00 | No: one continuous block | None | 4 |

## Rowan's explicit selection rule

Rowan accepts the priority order 1, 2, 3, 4, with 1 highest. Within a priority, use the earlier deadline; if deadlines tie, use the lower numeric task ID. The resulting order is **T01, T02, T03, T04, T05, T06, T07**.

Reserve fixed commitments first. Consider tasks in that order, retaining earlier reservations. Place the whole task at the earliest legal time that fits its duration, dependency and deadline. For T03, use the earliest legal allocation of all 90 minutes in one or two blocks, with each block at least 30 minutes. Never place only part of a task and call it scheduled. If the task cannot fit, leave it unscheduled with its full estimate and continue to the next task; a lower-priority task may use a gap that cannot hold the higher-priority one. Do not move earlier reservations merely to fit a later task. This is Rowan's chosen planning rule, not a claim of globally optimal scheduling.

Report the whole day, including unallocated time. For each of the seven IDs, report scheduled and unscheduled minutes and a reason. Unscheduled means **not allocated in this plan**, not canceled, completed or booked for another day. Only Rowan may change estimates, priorities or deadlines, permit a different split, or agree to a new commitment. Make those changes explicit before replanning.

----- COMPLETE CHANGE INPUT U1 -----
U1 — a new fixed commitment, received before work

At 08:45 UTC on 14 May 2030, before the 09:00 work window begins,
Rowan adds an equipment walkthrough from 13:00 to 14:00 UTC that day.
Assign it fixed ID F05. It lasts 60 minutes and cannot move or shorten.
The four original fixed commitments and all seven task inputs remain unchanged.

Produce V2 for the WHOLE 09:00–17:00 day using the same selection rule.
Nothing from V1 has been executed. Do not mark morning blocks complete,
freeze them as actual history, or pretend that the walkthrough happened.
Retain every task ID, estimate, deadline and dependency. Show the full new
day, every task's disposition, changed blocks and capacity arithmetic.
Do not write to any real calendar, create an ICS file, send invitations,
set reminders, book tomorrow or claim actual work completion.

----- COMPLETE AUTHORED WRONG VERSIONS -----
# 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.