How it works
A conversation can ask. Only a person can change the trip.
Every part of the trip page, the assistant included, can only ask for a change. The server prepares a review from its own copy of the trip, and the trip record changes when a person applies that review.
A change waits for a person
A part of the page asks for one kind of change, such as moving a planned item. The server checks that this part may ask for it, that the trip is in the right phase, and that nothing it depends on has changed. It then shows a review with each before and after. Applying the review writes the change with a record of what it touched. That record can be undone while nothing later has touched the same thing.
The assistant goes through the same door. It can ask the page to show one of 5 parts, and it can ask for a review. It is never given who is acting, what they may do, or the version numbers the server checks, and it cannot move the trip to another phase.
One phase at a time
A trip is in one of five phases, and each phase decides what can change. In Discover a wish the client stated can be confirmed. In Plan the day is built. In Confirm a step with a supplier is recorded and a stop can still be moved. In Travel a stop can be moved and nothing else. In Return what is kept about the client is decided. The trip goes on to the next phase through a review, and the way back is an undo of that move.
What the trip remembers
The trip keeps accepted changes, reviews that were set aside, and the review that is waiting. Each entry says who prepared it, which phase the trip was in, how it is known, and whose view it changed. Confirmed means a person applied a reviewed change. Stated means a person did something that left the record as it was. Observed means the page noted it, and it stays evidence until a person confirms something from it.
Behind the scenes is off until you turn it on
- Nothing about what you open or look at is noted unless you turn Behind the scenes on, and the server refuses a note while it is off.
- A note names a kind of thing and at most one item on this trip. It has no text field.
- Notes sit beside the trip record. They change no version, and the assistant is never given them.
- A trip keeps at most 200 notes. You can clear them at any time, and they are removed with the sample trip.
What is kept about a client
In Return, the page lists what was looked at more than once as a suggestion, with what it rests on. It becomes a client fact only when a person keeps it through a review, for this trip or for every trip. The server writes the fact from the suggestion it holds, so the page chooses only which suggestion and how widely it applies.
The assistant cannot ask to keep a fact or to stop keeping one, and it is never given one. No traveler view and no supplier view receives one. A person can stop keeping a fact, through a review, and the trip's history still shows that it was kept. This sample has no step where a traveler sees or agrees to what is kept.
The sample has a second trip for the same family. It can be opened once the first is in Return, and it starts in Discover with the facts that were kept for every trip, each marked with the trip it came from. A fact kept for this trip only is left behind. Nothing else crosses from one trip to the next: no wish, no recorded step, no note and no history. A change to the lasting pace does not cross either, because the second trip starts from the sample's own client record. A carried fact is part of the second trip's record and is removed with it.
What was asked of a supplier
In Confirm, an advisor records how far each request has got: asked, answered, confirmed. Each step is a note about something done somewhere else. Recording one contacts nobody, and it waits for a review like any other change. The step keeps the time it was recorded for, so when the plan moves later the page says the two no longer match.
Dates to ask by are counted back from the trip date. Nothing reads today's date and nothing watches the calendar, so the list never says that a date has passed. The assistant cannot record a step, and no traveler view and no supplier view receives one.
The day itself
In Travel, the page shows the day with a clock you move yourself. It reads no real time and no location, and it is never sent anywhere. One scripted change on the day can be repaired with a reviewed move, and the server works out the new time. What changed is then listed once for each audience, holding only what reached it. Entry rules are not assessed in this sample, and the page says so.
What is answering in the assistant panel
A live model is configured on the server. Each run is metered and capped, and every change it proposes waits for a person.
A live model needs an explicit server model, key, prices, and a daily spend ceiling. There is no visitor toggle and no default price. Every run is claimed once, capped, and settled, and a repeated run is refused. A run that ends without reporting what it used keeps the whole amount that was held for it.
CopilotKit Intelligence is refused in this build. This sample has not been cleared for an uncapped public launch.
What this sample is, and what it leaves out
- Synthetic sample trip
- Every change is reviewed by a person
- Nothing is booked, sent or paid for
It has no live place search and no supplier connection. The readiness example stays on the private bench until its reference material may be redistributed.