Class is only the first layer of your Ticket.

TICKET METADATA & SHIP EVENTS

Two passengers can hold the same class of RAOLAX Ticket and still travel through a different story.

Every Ticket is intended to be unique. Beyond class and Founder Weight, its metadata can describe where you are aboard RAOLAX, what kind of space you occupy and other attributes connected to your journey.

Most days, a cabin number is simply a cabin number.

Then RAOLAX enters a new system, the lights change, an announcement reaches only Deck 7 — and suddenly a detail that looked decorative becomes the reason your wallet is eligible for something nobody else aboard can claim.

That is the idea behind RAOLAX metadata events: **your Ticket is not only a class. It is a place inside a travelling world.**

— Ticket class;

— deck;

— sector;

— cabin or room number;

— side or orientation of the ship;

— room type;

— family / group attributes;

— proximity to facilities or locations aboard;

— role or profession tags;

— Crew function where applicable;

— other attributes introduced for the RAOLAX world.

Future RAOLAX Events can select one attribute, several attributes together, or another published eligibility rule.

Metadata does not guarantee a reward. It creates a vocabulary the ship can use to recognise different passengers in different situations.

Ticket class controls major Founder mechanics such as Ticket Weight, Founder Drop Degree and some priority layers.

Metadata adds another dimension that does not have to follow price.

A Regular Ticket on a particular deck can be more relevant to one event than a VIP Cabin somewhere else. A sleeping Cryo passenger can still match a metadata event before awakening. A Crew role can matter because of what is happening aboard rather than because of its market equivalent.

This allows RAOLAX to remain a world rather than becoming a spreadsheet where every outcome is determined only by how much somebody paid.

RAOLAX is not treated as a generic container holding 1,000 identical NFTs. The ship can have decks, sectors, cabins, common areas and facilities that create a spatial layer for events.

Imagine RAOLAX approaching a star system visible only from one side of the ship. Cabins facing that direction receive an observation event.

A temporary power problem affects a particular sector. Passengers there receive an emergency-related opportunity.

A celebration takes place near a banquet area. Nearby cabins become eligible for a small surprise.

These examples illustrate the mechanic rather than promise specific future events. The important part is that **location metadata gives the story somewhere to happen.**

An event does not have to target everyone who shares one attribute.

RAOLAX can combine metadata:

FAMILY CABIN + DECK 4

CREW + MEDICAL ROLE

PORT SIDE + SECTOR C

REGULAR + CABIN NEAR OBSERVATION DECK

CRYO + SPECIFIC MODULE

A combination can create a much smaller eligible group and make otherwise ordinary metadata unusually significant.

This also means two Tickets of the same class can develop very different histories over the journey.

A VIP Cabin can be imagined as enough space for a family, team or close group rather than simply a more expensive seat.

Metadata can reflect that distinction. A family or group attribute can later become relevant to social events, group experiences, special distributions or other story mechanics where travelling together matters.

The attribute itself does not promise a fixed benefit. It gives MUTERRA a persistent way to recognise that this Ticket represents a different kind of place aboard.

Crew Passes are different because every Crew Ticket can have its own artwork, concept and role connected to the contribution through which it was earned.

A creator, promoter, technical contributor, community organiser or another useful participant may therefore carry metadata that reflects a function rather than a passenger luxury class.

Future Crew-only Drops or events can use that information where appropriate.

A Crew Ticket should feel less like “Seat 418” and more like an actual personnel record aboard a ship whose passengers are building something together.

Cryo deliberately misses regular scheduled Founder benefits before awakening in Q3 2027. It does not accumulate missed quarterly MUTA distributions or scheduled Founder Drops.

But the Ticket still exists aboard RAOLAX.

Where a random event, metadata event, lottery or surprise mechanic explicitly includes Cryo, a sleeping passenger can still become eligible. The event may care about the pod, sector, metadata combination or simply the fact that somebody is aboard — not whether that passenger is awake.

This preserves the difference between **scheduled Founder benefits**, which Cryo postpones, and **ship events**, which can occasionally reach the cryogenic decks anyway.

Weighted Draws use probability and Ticket Weight. Metadata Events use attributes and event-specific eligibility.

A Bridge Seat can have 100× weight in a Weighted Draw and still be completely irrelevant to an event targeting family cabins on another deck.

A Regular Ticket can have 1× weight and be one of only five Tickets matching a rare metadata combination.

The two systems can also interact if a future event explicitly says so — for example, metadata could define the eligible group and Ticket Weight could then determine entries inside that group. But that combination should be stated in the rules of the event rather than assumed.

The most interesting long-term possibility is not a single reward. It is continuity.

If a Ticket participates in notable RAOLAX events over several years, its cabin, role and transaction history can become part of the provenance surrounding that individual Founder asset.

A Ticket can change wallets without becoming a different cabin. The holder changes; the origin and event history of the asset can remain connected to it where MUTERRA records those events.

Over a 10–20+ year project, that can turn an apparently small metadata field into part of the history of an object.

RAOLAX Events can be used for more than distributions.

An event might unlock lore, a visual change, an access window, a collectible, a task, a community role, a game opportunity, a cinematic fragment, a claim, a draw entry or another experience connected to the world.

Some events may simply become part of the recorded journey.

This matters because RAOLAX should not feel like a machine that periodically pays wallets. It should feel like a ship carrying 1,000 finite Founder positions through a story that continues while MUTERRA is being built.

If every metadata combination and every future event were published in advance, passengers would optimise only for known rewards and the world would stop feeling alive.

MUTERRA can therefore keep some future RAOLAX Events, combinations and triggers undisclosed until they occur.

This does not mean changing historical Ticket metadata after the fact simply to choose winners. Eligibility should follow the metadata and rules applicable to the event.

The uncertainty is in **what will happen**, not in secretly rewriting who you were aboard the ship.

A rare metadata combination does not guarantee market value, a future reward or greater financial return.

Some attributes may become relevant many times. Others may never trigger a material benefit. Their role can be aesthetic, narrative, functional or simply part of the uniqueness of the Ticket.

That uncertainty is intentional. The metadata system gives MUTERRA room to build future experiences around a finite set of Founder objects without pretending today that every attribute already has a known economic outcome.

Metadata tells the story something else: **where you were when it happened.**

Maybe your cabin never becomes important. Maybe one ordinary attribute puts you in the middle of an event years from now. Maybe a combination nobody paid attention to becomes part of a story shared by only a handful of the original 1,000 Tickets.

That possibility is why every RAOLAX Ticket should be more than a serial number.

The ship has geography. The passengers have positions. The journey has events.

And the manifest remembers.