SoReady™
The Continuity Layer for Major Events

The functions of a major event are generally well equipped: finance, planning, accreditation, sport, security, logistics or documentation. Yet none of them alone carries the decisive question: can the whole thing work, on the planned date, with confirmed means and the required evidence? SoReady addresses this horizontal discontinuity. It makes visible the dependencies between domains, the contradictory information and the decisions left without an owner.

SoReady's positioning rests on one discipline: not reproducing the depth of specialist tools. The financial system stays authoritative for commitments; planning for dates; document management for documents; sport solutions for their own objects. SoReady assembles the reading management needs: obligations, states, impacts, reservations, evidence and decisions. This complementarity reduces migration risk and allows progressive adoption.

An isolated piece of data does not produce a reliable decision. It must be qualified, linked to an object and checked against applicable rules. The SoReady chain preserves the path from source to evidence: who supplied the information, which version was valid, what calculation ran, and who arbitrated. This continuity makes it possible to explain a decision after the fact and to revisit it when its context changes.

The order of the modules reflects an order of trust. Governance and security define first who can see, modify or validate. The knowledge layer turns documents and reference data into sourced facts. Preparation connects planning, infrastructure, FoP, resources, budget, BOM, VIK and risk. Finally, the EOS and the Event Data Fabric support operations. Modules can be activated separately, but they share the same grammar of objects and evidence.

The breakdown does not describe thirteen juxtaposed applications. It exposes the capabilities needed to move from a documentary obligation to an opening condition, then to a live situation. Budget, BOM, VIK and workforce give substance to the means; planning and contention verify their availability; Risk Assessment measures exposure; EOS/EDF observes the signals. Reporting and cross-checked AIs make this information readable, without modifying certified data on their own.

OCR is only the first step. SoReady must distinguish detected text, proposed fact and validated information. A requirement extracted from a regulation is matched to a discipline, a venue, a date and an owner; the original excerpt stays accessible. When a version changes, the system identifies the affected objects instead of silently overwriting the previous knowledge. Automated population thus becomes a controlled accelerator, not a source of opacity.

Contention appears when the same resource is promised to several incompatible sequences: space, team, equipment, transport, power or turnover time. The engine cross-references calendars with real capacities and dependencies. It does not stop at flagging a collision; it prepares arbitration options with their effects on budget, VIK, workforce and readiness. Management can then decide before the conflict reaches operations.

The EOS provides an operational representation of the event; the EDF feeds it qualified events from heterogeneous domains. Between the source and the business state, a governed exchange zone checks the identity, form, authority, sensitivity and timing of the signal. Accepted events stay attached to their evidence and can be distributed, replayed or isolated. Correlation then surfaces a situation that no single source, taken alone, could reveal.

The EDF industrialises the lifecycle of a signal. It records the flow's contract and its owner, controls admission, keeps a proof or a probative reference, quarantines non-conforming messages and distributes accepted events to independent consumers. Deduplication, replay, recovery after an outage and store-and-forward protect continuity. A canonical contract then enables explainable correlations without overwriting the authoritative source. The module evolves source by source without destabilising the EOS.

Sport, results, weather, mobility, crowd, medical, security, OT, IT, logistics and media evolve at different rhythms. The value of the EDF is to preserve this diversity while giving it a common timeline. The demonstration scope covers several dozen flow families and multi-domain scenarios; it remains extensible. The value lies less in the number of connectors than in the ability to qualify the freshness, confidence and operational impact of each signal.

Security runs through the product: identity, rights, confidentiality, integrity, availability, continuity and audit. ISO 20121 structures responsible event management but does not on its own cover cybersecurity. ISO/IEC 27001, ISO 22301 and the OWASP frameworks therefore complete the approach; ISO/IEC 42001 addresses AI governance. SoReady can support the evidence and controls of a programme, without turning this alignment into a certification claim.

The choice between external, hybrid or sovereign AI depends on the data and the context, not on an abstract technology preference. Public or low-sensitivity content can use a controlled service. Contractual, financial or operational data can be routed to a private environment. Critical functions or those with strong continuity requirements can run locally. An MCP-type tool gateway can preserve common access contracts. In all three cases: minimal context, visible sources, bounded actions and human validation.

All complex events share invariants: programme, venues, sequences, owners, resources, rules, risks and evidence. SoReady stabilises this grammar, then configures the vocabulary and obligations of the context. An international competition emphasises disciplines and FoP; a summit, delegations and protocol; a festival, stages and permits. Universality therefore comes from a coherent core and explicit contextualisation, not from an impoverished generic model.

Openness to the outside is only reliable if the boundaries are administrable. Functional administration configures taxonomies, workflows, gates and responsibilities. Technical administration operates connectors, performance, backups and observability. Security enforces identities, separation of duties and integrity controls. This organisation makes it possible to accept external flows without delegating authority over the programme's objects to them.

A useful deployment starts with a management question, for example the readiness of a cluster or the turnover of several disciplines on one venue. The first thirty days align objects, owners and sources; the next connect documents, dependencies and rules; the final step demonstrates a gate with evidence and arbitration. This pilot produces verifiable value and reveals data gaps before extending to all functions.

The standards and frameworks cited provide complementary angles: event management, risk, continuity, security, AI, provenance and accessibility. They make it possible to check that the architecture does not overlook a major dimension. This document does not reproduce their normative content and does not claim to demonstrate compliance. Any certification is a matter of scope, a management system and a formal audit.