A family holiday

The framework master reference used a seven-day family holiday — a couple in their late forties, a daughter of eighteen, a son of twelve, a fixed budget — as its universal example. It did not make it into the narrative. It belongs here, because it is the case a parent will recognise first.

Planned for release phase 2. The page is complete as a draft; interactive parts run in the browser and do not yet save to an account.

In brief

This case is laid out against the eight steps of the framework. Jump to Step 1 to see how the end state was defined, or to Step 8 to see what integration caught.

  1. Define the End State

    Alone, before opening any app: what should this week feel like for four people who want different things? Not "seven days in Kerala" but "the eighteen-year-old comes back having had one experience that was hers, the twelve-year-old is not bored for more than an hour at a stretch, the two of us get two unhurried evenings, and nobody is doing arithmetic at dinner."

  2. Map the Flow

    Your own list first: dates, budget, travel, stays, what each person wants, the one non-negotiable each has. Then AI reviews it: what have you not thought of? Typically — buffer days, the temple closed on the day you planned, a late-arriving flight that eats the first evening, meal logistics for a family that argues about food.

  3. Assign Tasks

    Deciding what the week is for: human. Generating twenty itinerary options within budget: AI. Choosing among them: human. Checking opening days and distances: AI, verified. Persuading the twelve-year-old: human, unavoidably.

  4. Select the Tool

    A conversational model for the plan (iterative, medium context); a tool with live web access for anything factual — timings, prices, closures.

  5. Prepare and Direct

    The tool is briefed like a travel agent who has never met the family: ages, preferences, budget, energy levels, what went wrong last time. The success criteria written first: total under budget, no two travel days in a row, one thing per person that is theirs.

  6. Execute

    The plan is built. Bookings are made by the humans.

  7. Evaluate

    Against the criteria — and the plan fails one: three consecutive days of driving. Iterate.

  8. Integrate and Stress-Test

    Small fixes: a shut restaurant, no buffer before the return flight — just fix them. Structural: the budget does not add up once real prices land, and fixing one stay breaks the sequence. Trace to Step 2: reprioritise the whole flow rather than patching the night that overran.