Four US domains, one ambiguous request — so AOS asked instead of guessing
A premium spa and hot-tub brand operating across multiple markets and domains sent a short request: 'we need an ad for the American domain.' But the brand runs several active US-facing properties. Rather than pick one and build confidently in the wrong place, AOS read the workspace structure, surfaced four active US domains, and asked the operator to choose. The right outcome here was a question, not a deliverable.
01 Ground
Multi-market brands accumulate domains the way old houses accumulate keys — there's the main US site, a market-specific variant, a legacy property still serving traffic, a sub-brand. To an outsider 'the American domain' sounds singular and obvious. Inside the workspace it resolves to several distinct entities, each with its own positioning, audience, and creative implications.
The dangerous version of helpful is the system that resolves this ambiguity silently. It picks the domain that seems most likely, builds a polished ad against it, and hands over work that is excellent and aimed at the wrong target. The operator then has to notice the mismatch, explain what they actually meant, and wait for a rebuild — slower and more frustrating than if the system had simply asked up front.
The real task was entity resolution: figure out which of the brand's US properties the request referred to. With four live candidates and no way to infer intent from the words alone, guessing wasn't efficiency — it was a coin flip dressed up as initiative.
- Four active US-facing domains identified within the brand's workspace structure Drive / workspace structure 2026-06-21 90% confident
- Request 'an ad for the American domain' — unresolvable to a single entity without operator input Workspace structure 2026-06-21 88% confident
02 Decide
AOS read the brand's workspace structure to enumerate the candidate entities rather than reasoning about which domain 'felt' right. It found four active US domains and recognised that no amount of cleverness could turn an ambiguous request into a confident target — the missing information lived with the operator, not in the data.
So it stopped and asked the operator to pick. This is a deliberate design stance: a system that won't fabricate also won't pretend to know which entity you meant. Disambiguating via the actual workspace structure — and naming the four real options — is more useful than producing a beautifully wrong ad, because it turns a guess into a thirty-second choice.
03 Deploy
AOS resolved the request against the brand's workspace structure, enumerated the four active US domains as concrete options, and returned the choice to the operator rather than proceeding on an assumption.
No creative was generated yet — by design. The deployment pattern here is a clarifying gate: when a request is ambiguous at the entity level, surface the real options and let the operator collapse the ambiguity before any downstream work spends effort in the wrong direction.