Context sensitivity
Does the support reflect the conditions and constraints that shaped the situation?
Saudi Arabia / ARHAB
Operational Intelligence & Decision Support Layer
Clearer decisions as event crowds move.
ARHAB is a human-led operational intelligence layer for sports venues and major events. It works above existing systems, connecting the operating situation and its constraints with relevant context and bounded decision options.
Pre-prototype · synthetic cases · no live integrations
01The operational question
Keep the context behind the decision.
When event crowds begin to leave, a venue team must interpret the current situation alongside local constraints. Later, another team may need to understand what was decided, why it fit the conditions, and what followed.
ARHAB explores a structured way to connect operating state, constraints, evidence, decisions, actions and outcomes—so relevant context can be considered again when similar situations arise.
02First validation case · pilot v0.1
Focused starting point
Post-event crowd egress at a stadium or venue.
The initial design is being shaped around a venue or event duty manager. It explores how to build a shared view of the operating state, identify a bottleneck, compare bounded response options, and record the selected action and outcome.
Primary userVenue or event duty managerCurrent test basisSynthetic operating cases
Proposed operating loop
From situation to learning.
Decision context stays visible at each step. The responsible operator retains authority throughout.
- 01
State + constraints
What is happening, and what limits the available response?
- 02
Relevant context
What evidence and prior experience match this situation?
- 03
Bounded options
Which evidence-supported responses may fit the conditions?
- 04
Human decision
The responsible operator reviews, adapts, or declines an option.
- 05
Action + outcome
Record what followed and the lesson for a similar context.
What the pilot is designed to validate
Evidence discipline
Can each option be traced to relevant evidence, with uncertainty made clear?
Operational learning
Can the selected action and outcome help the next team reason from experience?
Current stage: pre-prototype design using synthetic cases. No live venue data, production integrations, autonomous control, or field-performance claims are part of this stage.
03Governance by design
Design principles under validation
Useful support, within clear limits.
These are proposed safeguards for the pilot design. Their effectiveness must be tested before any operational use.
Evidence stays visible
Show the supporting context and why a prior case is relevant, including material differences.
Options stay bounded
Present only options supported by the available evidence and operating constraints.
Uncertainty is stated
When the evidence is insufficient, explain the gap and switch to evidence-only support.
People retain authority
Operators make the decision. ARHAB does not issue commands or control infrastructure.
Existing systems remain in placeData remains under the responsible entity's ownershipActions are recorded for review and learning
04Scope and direction
First focus
Start with one operating scenario.
The first validation case is post-event crowd egress in a sports venue. Broader application depends on learning from this focused work and validating operational need with relevant users.
CURRENT SCOPE 01
Potential future contexts
Areas to explore after validation
- Mobility and visitor flows
- Workforce and logistics
- Telecom and network signals
- Safety, health and operational signals
- Fan and visitor experience
- Cross-entity operations
These are longer-term contexts, not part of the current pilot scope.
Institutional enquiries
Build operational intelligence from experience.
For institutional discussions, venue and sports-operations validation, and strategic collaboration.