Imagine arriving at a destination where the language you chose follows you between participating experiences. A membership preference is available when you want it, and an operator can see why a system proposes a change. The place feels coherent because its systems work from compatible information and defined permissions.
That is the design ambition explored in this December 2025 perspective. It begins with information people choose to provide and the integrations a venue actually authorizes. Recognition alone cannot establish someone’s language, interests, allergies or access needs.
Continuity across the experience
A venue may have separate ticketing, content, control and operational systems. Each knows something different. Useful coordination means deciding which information is relevant to an action, whether it is current and who has authority to use it.
For a guest who opts into membership continuity, the project can define which preferences persist and how the guest changes or removes them. For a visit-only experience, continuity may be limited to that session. Cross-venue continuity needs explicit agreements, consent and integration; it should never be assumed merely because two venues use the same platform.
Where WorldModel fits
WorldModel™ is the governed operating architecture that gives these relationships a common structure. The current reference brings together ten layers and eleven cross-cutting policies. It covers the venue’s values and constitution, proposed actions, changing state, bounded authority and evidence.
Mad Intelligence™ is the wider ambition of preserving design intent through continuing engineering. WorldModel provides the governance and shared-context architecture; AV++® brings the technology family; QuickSilver® supplies the computer-based playback and control foundation. Mad Hatter™ adds a DSP platform with capabilities that extend beyond conventional processing. Each has its own implementation and development scope.
TECHNICAL DETAILMake a proposed action explainable
Open the engineering detailClose this sectionLook for the red circuit symbol for engineering detail.
In an illustrative gallery scenario, a visitor chooses a quieter route. A connected system would need the visitor’s permission, current route availability, relevant operational constraints and an authorized means to present guidance. It should be able to distinguish a requested preference from an inference and a proposal from an executed action.
The reference architecture describes how those responsibilities fit together. It does not establish that every published pattern is already connected to every Mad installation. WorldModel.global remains the current source for the definitions.
A roadmap with clear starting points
Portable credentials, cooperation with a visitor’s personal AI and additional spatial or sensory adaptations are directions to evaluate as their interfaces and governance mature. They should be discussed as planned or developing work where that is their status.
WorldModel: Patent pending. A project conversation should identify the working functions to demonstrate, the integration to engineer and the acceptance criteria that will show whether the intended experience has been achieved.