№ 006 · 2026-07 · shipped · context and a browser

Operation summer camp

familyplanningclaudeamazon

Our daughter did her first week of sleepaway camp this summer — a camp on the east end of Long Island. She loved it. Getting her there turned out to be the clearest demonstration yet of the difference between a chatbot and an assistant that actually knows your family.

Research, then vigilance

Claude did the initial sweep — programs, sessions, dates cross-checked against our travel, what past parents said — and produced a short list with trade-offs. We picked; the machine narrowed.

Then it stayed on duty: constantly re-checking the parent portal to confirm every requirement was actually met — doctors’ forms, immunization records, the whole checklist — so nothing expired or sat unsubmitted while we weren’t looking. Camp paperwork is a shifting compliance target; having something re-verify it beat trusting that “done in May” still meant done in July.

The packing list, done in one evening

Here’s the part I keep telling people about. The camp’s packing list was dozens and dozens of items. The usual family protocol for that is a week of debate, three store runs, and a night-before scramble.

Instead: Claude already knew our daughter — her age, her sizes, her likes and dislikes — because it’s all context in the family workspace. It cross-referenced the camp list against that and gave me a quick rundown of what it figured we’d need. I told it the short list of things we already owned — which was very little. Then it went shopping: bargain-hunting across options, matching her known preferences, and loading the picks directly into the Amazon cart through the browser.

Sara and I reviewed a cart of 50–60 items, swapped maybe two or three, and hit submit. Everything arrived within two or three days. Our daughter saw the haul the same time we did — no debates, no negotiation, a total non-issue. Verdict on the packing job: slightly over-prepared, never once under.

The two items that made it personal

A packing list is generic. Context is not. Claude knew where the camp was, what the weather would be, the terrain, the activities — and that knowledge showed up in the cart in two ways I still call out:

That’s the whole thesis of this blog in two line items: the value isn’t that the machine can shop. It’s that it knows your situation well enough to disagree with the packing list.

One more save

While wiring the trip around camp, re-verifying every reservation against source data caught that the airline had quietly moved our flights — and that a car return was now booked on the wrong side of the new departure time. One rebooking from the couch instead of a disaster at the counter. Re-validate everything after any change — deploy rules apply to vacations.

Aftermath

She’s already asked to go back, so next summer’s iteration is underway — longer this time, with a couple of alternatives being scouted. The dependency graph is already drawn. This is what winning looks like in family ops.