Back to Venueweave

Research and design boundary

Venueweave's venues, group names, distances, capacities, sign budgets, maps, incidents, and solutions are original fiction. No source supplied a layout, a capacity figure, or a puzzle. What the sources below informed is narrower and honest: that step-free access is a design requirement rather than an optional extra, that a corridor has a finite safe throughput, that opposing movement in a narrow passage is a recognised hazard, and that wayfinding is a limited resource that has to be spent deliberately.

References

What the game deliberately does not model

Capacity here is a single integer per link. Real capacity depends on width, gradient, surface, door and stair geometry, flow rate over time, evacuation timing, staffing, and jurisdiction, and it is calculated by qualified people against a specific code. Venueweave has no time axis at all: everyone in a group is treated as arriving at once and the corridor loads are static sums. It models no queueing, no doors, no lifts as a limited resource, no evacuation, no fire, no weather, no staffing, and no signage legibility. The resilience desk adds fifteen percent to every group and re-checks the same static rules; it is a comparison aid, not a safety margin.

Venueweave is not planning software and must not be used to justify a decision about a real building or a real event. Consult a qualified access consultant and the safety authority for the jurisdiction.