business-event-formatslisted

# Business Event Formats You pick which company-run event shape a company runs this year: invite-only dinner or roundtable, executive summit, single-city user conference, multi-city roadshow, or floor-primary event. Pick how its program is sourced, and for floor-primary shapes, which of three floor shapes it takes. Decide the shape and stop. Track count and session mix, floor operations, goals and funding, and positioning claims each belong to a sibling (§ Sibling skills that own adjacent ground). Never re-derive them. Say **company-run** and **community-run**. Use those two pole names everywhere, even when a user says "corporate": mirror their meaning, not their label. ## Sizing constraints State no headcount, city count, agenda length, ticket price, or budget figure, here or in any deliverable built from this skill. Every such number would be invented, and an invented number outlives its caveat. Every effort, value and compliance ordering below is argued from these shapes' mechanics and contestable on its own terms: a reasoned default, not an industry ranking. ## Sibling skills that own adjacent ground - **`samber/dev-event-organizer-skills@event-format-selection`**: owns the community-pole shape ladder, track count, session mix, delivery mode and hackathon demo structure. It hands "the vendor-side format family in depth" here by name. Once the shape is named, track count and session mix are its decision, not this skill's. - **`samber/dev-event-organizer-skills@even