Message in transit
Research project · In development

Engineering trust across time

Some words belong
to the future.

You leave a message for someone to open in 2076.

The service closes in 2046. Who delivers it now?

Perlatum is researching how the person you chose could find your message, verify that you wrote it and open it on your terms, even if Perlatum itself is gone.

Thought experiment

A message for 2076.

You can hand a letter to a friend today. Then someone has to keep it safe, find the right person and remember when to give it to them. You can schedule an email, but who will own that inbox decades from now? Imagine leaving one message to cross that distance.

2026

A message is sealed.

Your daughter is six. You write down why you made a decision that shaped her childhood. You want her to have your own account in 2076, when you may no longer be there to answer her questions.

Count fifty years back from 2026. In 1976, the first web server was fourteen years away. Gmail was twenty-eight years away. Now look the same distance forward.

The original service

2046

The company closes.

The login stops working. The team disperses. If the original service alone was scheduled to send your message, delivery stops here. A backup might still hold every word.

Thirty years from now, no reminder will come from that service. What would your daughter need outside the company to find the message and open it on your terms?

The copy survives. The scheduled delivery stops.

2076

The date arrives.

Your daughter is now fifty-six. Her surname has changed. Her childhood inbox is gone. Among the family papers she finds instructions for a sealed message. Where can she find the copy, and how can she prove it was meant for her?

Even if she finds it, she needs a way to check that these are your words and that you never withdrew permission. That is what the research has to make possible.

Independent recovery?
The original service

What happens when
we switch Perlatum off?

Your daughter has kept a sealed copy for decades. The design gives her a reader she can run on her own device. If you cancelled the message after she saved it, how would that reader know?

In a local simulation, we switched off the company service. A separate reader compared a portable test message with a trusted record of the sender’s latest instructions. It recovered the original text and rejected both an altered copy and an out-of-date one.

We supplied the trusted record ourselves. After a real shutdown, your daughter would need a way to find that record and verify that it was still current. A full recovery drill with the operator offline is still ahead.

Current scope

We’re starting with text. The initial design lets a sender choose a future date or a defined period of inactivity with check-ins, warnings and a grace period. Audio and video are longer-term goals.

The proposed experience

Leaving a message. Receiving one.

Choose the person and the rule. The design encrypts the message on the sender’s device.

If you’re leaving a message

  1. Write the words and name the people.

    Choose one person or several. Decide who should receive each message. The design calls for encryption on your device before a copy leaves it.

  2. Decide when it may open.

    Choose a date or an inactivity rule. Review the people, the condition and what happens if you lose access. Once sealed, the words are fixed. A revision needs a new version.

  3. Keep a way to act later.

    Save the recovery materials and protect your credentials. You may need them to confirm activity or cancel. A cancellation must take effect before release is authorized. After that, a message cannot be recalled.

If a message is for you

  1. You may learn about it while it is sealed.

    An advance notice could let you prepare even if you have never had a Perlatum account. You could keep the encrypted copy and instructions, and protect your private credentials separately. Early notice gives you no early access.

  2. You can still be the same person with a new device.

    Years later, a lost phone or old address may leave you unable to sign in. The recovery design must let you prove you are the person originally named. Someone who helps you recover access does not inherit your right to read.

  3. When the condition is met, establish your access.

    The design checks your identity and device before you can open the message locally and verify its origin and contents. Each recipient does this separately. If the operator has closed, its notices may have stopped. Independent recovery also needs surviving instructions, evidence and key holders.

Release conditions

When may a message open?

The sender chooses one of two rules in the initial design. Each sets the earliest point at which release can be authorized. The person named in the message still has to establish their own access.

On a date I choose

“Let my daughter read this on 12 November 2076.”

The message stays sealed until the chosen date and for at least seven full days after preservation is acknowledged. Both requirements must be met. This route has no quarterly check-in.

When the date arrives, the system must still verify the sender’s current instructions, check the message’s integrity and resolve any hold. An earlier cancellation can keep a surviving copy sealed.

If I stop checking in

“If I stop confirming that I’m here, give me time to respond before considering release.”

The sender is due to confirm every three calendar months. A missed confirmation starts a 30-day grace period with warnings. A valid confirmation resets the three-month clock if it takes effect before release.

If there is no qualifying evidence that the final warning reached a previously verified contact route, the message stays on hold, potentially indefinitely. An outage affecting the required services also pauses the process. Once service is verified and the process restarts, a fresh grace period and warnings follow.

Even after the grace period, the seven-day minimum and final checks still apply. Inactivity records missed confirmations. It cannot establish death, incapacity or disappearance.

Try the inactivity rule

Awaiting check-in

The message stays sealed. The next confirmation is due three calendar months after the last accepted one.

What about a wedding, an executor or more than one condition?

A known wedding date can use the date rule. Establishing that a wedding actually took place, giving an executor authority to trigger release, or combining a date with inactivity would each require a different design. Those options are outside the first product’s scope.

Possible applications

What would you leave, and for whom?

Some of these situations fit the initial text-message design. Others ask more of it, especially when someone’s safety, legal authority or a changing institutional role is involved.

Personal messages

A parent’s advice for an older childThere are things a six-year-old may only want to ask about at thirty.
Sender
A parent facing serious illness writes about a difficult choice they made when their daughter was small. They name her and choose her thirtieth birthday.
Recipient
Years later, she can hear the reasoning directly from the person who made the choice. The design gives her a way to verify its author even if she now has a different surname.
Condition and scope
A specified date. Written advice fits the initial text design.
A grandparent’s words across a generationA child may grow up knowing a grandparent only through other people’s stories.
Sender
A grandfather writes down the story behind the family name while he can still tell it himself. He chooses his grandson’s eighteenth birthday.
Recipient
At eighteen, his grandson could read the story in his grandfather’s own words. The friend who kept an encrypted copy for him would have no right to open it early.
Condition and scope
A specified date calculated from a known birthday.
A farewell when there may be no final conversationSomeone may know what they want to say without knowing when they will lose the chance.
Sender
A person undergoing treatment writes a separate goodbye to each of two friends. They choose periodic check-ins so the messages stay sealed while they continue to confirm.
Recipient
Each friend would gain access only to the message meant for them. A notice would say the sender’s chosen condition was met. It could tell neither friend what happened to the sender.
Condition and scope
Defined inactivity, with warnings and time for the sender to respond.
An anniversary or another known occasionSome words belong to a particular day, even if both people are still here.
Sender
On their first anniversary, one partner writes down the ordinary things they hope they will still remember on their twenty-fifth. They select the anniversary date.
Recipient
Their partner could read an account written at the beginning of their life together. Opening it depends on the chosen date, regardless of whether the sender is still checking in.
Condition and scope
A known calendar date. Detecting a wedding or another future event would require additional work.

Memory and continuity

A time capsule for people who were thereThe memory of a shared moment changes with every retelling.
Sender
On the last night before their friends move away, someone writes down what each person hopes to be doing in twenty years. They name the friends and seal the letter for a reunion date.
Recipient
Each named friend could compare those hopes with the life they lived. If one friend has lost a device, the others can still establish their own access.
Condition and scope
A specified date and individually named recipients.
A family history in the voice of its witnessA photograph survives, but the person who knows who is in it may not.
Sender
An aunt writes down why her family left their hometown and which details have been lost in later accounts. She chooses the people who should receive her version and when.
Recipient
Her relatives would have her first-person account and a way to check its origin. Hearing her pronounce the place names herself is a reason to explore audio preservation.
Condition and scope
Individual text accounts fit the first design. Shared archives, audio and video are future possibilities.
Practical instructions after someone becomes unavailableKnowing a document exists is different from knowing where to find it.
Sender
Someone leaves their sister a note explaining where the family papers are kept, who holds the originals and which relative can explain them.
Recipient
The sister would know where to begin looking. Receiving a private note gives her information. Legal authority over the estate is a separate matter.
Condition and scope
A specified date or defined inactivity. Executor-controlled release and legal integrations are outside the initial scope.

Professional and public-interest work

A founder’s account of a decisionA successor may inherit the paperwork and still have no idea why a promise was made.
Sender
A founder records why the company agreed to support an early customer on unusual terms. They designate a successor and choose release after prolonged inactivity.
Recipient
The successor would hear the founder’s reasoning, including the part missing from the minutes. The message itself gives them no new company permissions.
Condition and scope
Private text instructions fit the initial design. Team accounts and succession workflows are future work.
An account entrusted to a journalistFor a confidential source, opening a message too early could put someone in danger.
Sender
A source might want a named journalist to receive an account if regular contact stops. Before trusting such a system, the source would need to understand who could learn that the message exists and what happens if a warning never reaches its destination.
Recipient
The journalist would need to establish who wrote the account and whether it changed. Publication would remain a separate editorial decision.
Condition and scope
A future protected-disclosure application. Safe notice, source protection and professional handling need dedicated work. Silence cannot establish disappearance.
Institutional memory beyond the original teamA future custodian can inherit an archive after everyone who assembled it has left.
Sender
An oral-history team wants to preserve the context of a private collection for a future archivist, including who provided each account and the restrictions agreed at the time.
Recipient
Decades later, the archivist would need to verify those instructions and establish their own authority as custodian. An old staff email address would prove little.
Condition and scope
A future organizational use. Access tied to a changing role needs rules beyond naming an individual recipient.

What must survive
the journey?

Keeping the file is one part of the work. The recipient also needs a way to establish whose words they are and when they may be read.

01

Privacy

Someone may need to keep a copy safe for decades. What prevents that person from reading it?

02

Authenticity

How can a recipient verify who wrote the message and whether the words have changed?

03

Release

What if the sender cancelled the message years ago, but an older copy still exists?

04

Continuity

Which records, people and tools must survive for recovery to work without Perlatum?

The name

Carried through.

Perlatum comes from the Latin perferre, to carry something all the way to its destination. For a message, that journey ends with the person it was meant for.

Research preview

Request an invitation.

Would you like to try recovering a sample message with the company service switched off? Leave your email for an invitation if the experiment opens to participants.

We’ll use your email only for research preview invitations. To withdraw your request, write to mail@perlatum.org. Privacy notice.

Work with us on
independent recovery.

We welcome conversations with researchers, infrastructure teams and strategic partners interested in testing what it takes for a private message to outlive its original operator.