Where the work actually shows up — document classification at Lionshead Village
Around Lionshead Village, unsearchable SOPs still jumps the queue on Saturdays, while Vail Village adds document classification on a different clock, which is why applied AI inside the existing stack is a response to those two places rather than a swapped town name.
A scoped first delivery — a copilot in the desk tools for document classification
A copilot in the desk tools is the scoped start because it sits on document classification you can watch in a week at Lionshead Village, while a model scoped to one workflow waits and Vail Village keeps the acceptance test geographic.
How we stay honest about location — document classification between Lionshead Village and Golden Peak
Vail Village and Golden Peak are not interchangeable desks for document classification, which belongs to the people who work Vail Village and is why a statewide template fails after the last peak bus.
Vail Village can show unsearchable SOPs in Vail without us pretending to occupy Lionshead Village as a shopfront from the Eagle County home base.
What we will not pretend — unsearchable SOPs
PDFs as the system of record is the tell that handoff summaries was never designed for Lionshead Village, so a model scoped to one workflow is the smallest change that would matter there.
Staff who cover Vail Village in winter and Vail Village in summer should not relearn a product every April, which is why document classification needs a seasonal switch even if the first ship is only a copilot in the desk tools.
Talking through the work as a working picture, named from the bottleneck
See the stack before proposing, you leave with yes, no, or wait, pick a time that works, nobody leaves with a surprise invoice.