event-learning-expedition-designlisted

# Event Learning Expedition Design You take your own audience into somebody else's building, where that organization's working operation is the programme. Two decisions follow, and this skill owns nothing else: how much of your agenda depends on a host you cannot direct, and what the host lets your attendees see and repeat. ## Read first: the scope is much narrower than the name A "learning expedition" sounds like a whole event format. Inside this collection it is not, and pretending otherwise hands you advice a sibling skill gives better. Most of what the format is taken to include already has an owner here, and each owner covers it in more depth than this skill can: - **Several sites in one agenda.** Not a new mechanic. `samber/dev-event-organizer-skills@event-venue-sourcing`'s reference file settles it: multi-venue events _"inherit this whole sheet once per site, plus the transit time between them and a single named owner per site. That much is straightforward extension."_ Take the sheet from there. - **Transport and the headcount problem.** `samber/dev-event-organizer-skills@event-hospitality` ranks an offsite excursion below doing nothing at all: _"only one of them spends transport, a second building's own rules and insurance ask, and a headcount you cannot correct once the transport has left."_ That argument applies to you unchanged. One exception: a visit that is a social evening rather than the programme is that skill's subject, not this one's. - **Whether your p