SUPERMARIO.WORKS LTD · Universal Builder System

07 — Macrosection 03 — Contact & Communication

Universal Accommodation Data Model v0.1

APPROVED WORKING DRAFT

Architecture Constitution v1.0: FROZEN · Architecture Consensus: 100% AGREEMENT · Implementation Design: OPEN

Purpose

This macrosection defines direct contact and communication capabilities for Accommodation objects while preserving the identity and engagement model of the territorial ecosystem.

Accommodation public presences are designed as professional native minisites within the relevant ecosystem, rather than as directory pages whose primary purpose is to redirect visitors to external websites or social networks.

Core principle: direct communication is supported, while external social networks and external websites are not standard public Accommodation contact fields.

A — Direct Contact Channels

Direct contact information belongs to the Accommodation communication model and must remain separate from account credentials and internal User System data.

Technical Key	Label	Description	Data Type	Required	Universal / Territorial	Public / Private	Editable By	Plan	Validation	Relations	Multilingual	Searchable	Filterable	API-ready
`contact_phone`	Telephone	Primary direct telephone contact for the Accommodation.	String	NO	Universal	Configurable	Authorised User / Admin	Capability	International phone format	Accommodation	No	No	No	Yes
`contact_email`	Contact Email	Direct email address for public or controlled Accommodation enquiries.	Email	NO	Universal	Configurable	Authorised User / Admin	Capability	Valid email format	Accommodation	No	No	No	Yes

Contact details used for the public Accommodation presence must not be automatically treated as User Account credentials or administrative contact information.

B — Messaging Channels

Messaging is designed as an extensible communication capability rather than a collection of permanently hard-coded application fields.

Technical Key	Label	Description	Data Type	Required	Universal / Territorial	Public / Private	Editable By	Plan	Validation	Relations	Multilingual	Searchable	Filterable	API-ready
`messaging_channels`	Messaging Channels	Structured collection of direct messaging channels associated with the Accommodation.	Structured Collection	NO	Universal	Configurable	Authorised User / Admin	Capability	Allowed channel types	Accommodation	No	No	No	Yes
`channel_type`	Channel Type	Controlled identifier of the messaging service.	Controlled Vocabulary	YES*	Universal	Internal	System / Admin	Capability	Allowed service	Messaging Channel	Labels only	No	No	Yes
`contact_value`	Messaging Contact	Telephone number, username or other service-specific contact identifier.	String	YES*	Universal	Configurable	Authorised User / Admin	Capability	Channel-specific	Messaging Channel	No	No	No	Yes

* Required only when a Messaging Channel record exists.

Initial supported channel configuration

WhatsApp — supported direct messaging channel.
Telegram — optional supported direct messaging channel.
Additional direct messaging systems may be enabled in future configuration without redesigning the primary Accommodation Data Model.

Adding technical support for a messaging service does not automatically make that service available in every territorial ecosystem. Allowed channels remain configurable.

C — External Websites & Social Networks

External websites and social-network profiles are deliberately excluded from the standard public Accommodation contact model.

Standard Accommodation minisites therefore do not require public fields for Facebook, Instagram, TikTok, X, LinkedIn, YouTube or an external business website.

This is a product and ecosystem decision, not a technical limitation. Future specialised integrations or partnerships may be implemented as separate capabilities or modules without changing this principle in the standard Accommodation contact model.

D — Ecosystem-Native Publishing Principle

Every public Accommodation presence generated by the Builder belongs to the specific territorial ecosystem in which that Accommodation participates.

Universal Builder System ↓ powers OXFORDSHIRE.world ↓ publishes OXFORDSHIRE.world/[accommodation-public-path] Puglia.world ↓ publishes Puglia.world/[accommodation-public-path]

The Universal Builder System provides the engine. The territorial ecosystem provides the public digital identity.

The definitive URL and routing structure is intentionally not frozen in this macrosection and will be defined during implementation and presentation design.

E — Ecosystem Engagement Principle

The public Accommodation presence is intended to build a direct relationship between visitors, participating entities and the territorial ecosystem itself.

External social networks are therefore not the default destination for engagement.

Not the default model: “Follow us on Facebook” “Follow us on Instagram” Ecosystem model: “Follow us on OXFORDSHIRE.world”

Future User System capabilities may allow registered users to follow Accommodation objects, places or other entities directly inside the ecosystem. Such functionality is not part of this Data Model release, but the architecture must not prevent it.

F — Minisite Communication Philosophy

The Accommodation presence must be capable of becoming a substantial, elegant and professional minisite inside the territorial ecosystem.

Communication should therefore rely primarily on the quality and depth of the native presence rather than on outbound links.

Relevant capabilities across the wider Accommodation Data Model include:

identity and classification;
professional descriptions and structured content;
rooms and units;
amenities and services;
accessibility information;
location and geographic relations;
photography and galleries;
video through the Media model;
specific content and editorial relations;
Campaigns and offers where permitted;
direct contact and messaging.

Photography and video are not Contact fields. They will be defined through Macrosection 11 — Media Relations using the already established Media Asset + Media Usage principle.

G — Separation of Public and Internal Communication

Public Accommodation communication data must remain conceptually separate from internal administrative contacts, User Account credentials, ownership relations and operational notifications.

PUBLIC ACCOMMODATION CONTACT Telephone Email Messaging Channels │ │ separate from ▼ USER / ACCOUNT / ADMINISTRATION Login email Account verification Ownership Permissions System notifications

User ownership and permissions are defined in Macrosection 04 — Ownership, Users & Permissions.

H — Macrosection Rules

03-R01 — Public Accommodation contact data is separate from User Account and administrative identity.
03-R02 — Telephone and email are supported direct communication capabilities.
03-R03 — Messaging is extensible through controlled channel configuration rather than permanent hard-coding of every messaging provider.
03-R04 — WhatsApp is supported and Telegram may be enabled as an optional messaging channel.
03-R05 — External social-network profiles are not standard public Accommodation fields.
03-R06 — External business websites are not standard public Accommodation fields.
03-R07 — Public Accommodation presences are native to their territorial ecosystem.
03-R08 — The Universal Builder provides the engine; the territorial ecosystem provides the public-facing domain and identity.
03-R09 — External social ecosystems are not the default destination for user engagement.
03-R10 — The architecture must permit future native follow/engagement capabilities without making them part of the current Accommodation release.
03-R11 — Media, video and editorial content remain outside the Contact model and are handled by their appropriate modules.
03-R12 — Definitive public URL structure is not frozen by this macrosection.

Practical Result

A participating Accommodation can maintain direct communication with its visitors through telephone, email and permitted messaging channels while building its principal digital presence inside the territorial ecosystem.

The intended result is not a generic directory entry followed by outbound social links. It is a native professional presence capable of growing inside OXFORDSHIRE.world, Puglia.world or another ecosystem powered by the same Universal Builder System.