MINDBEBOP
Mental Background OS
A bidirectional connection between the outside world and the Mental Background Layer.
Most communication inside MINDBEBOP stays inside the Mental Background Layer. MINDBEBOP apps can open one another, pass information locally, and continue Mental Steps across apps using on-device communication.
That is not a Cross-Dimensional Handshake.
A Cross-Dimensional Handshake happens when something crosses the boundary between MINDBEBOP and the outside world.
The handshake can move in either direction: an outside event can enter MINDBEBOP, or a supported MINDBEBOP event can be sent outward to a system chosen by the user.
An inbound Cross-Dimensional Handshake can bring an outside event into the Mental Background Layer through MindEvent. An outbound Cross-Dimensional Handshake can send a supported MINDBEBOP event to an external HTTPS destination.
Outside World
↓
Inbound Cross-Dimensional Handshake
↓
MindEvent
↓
Mental Background Layer
↓
Supported MINDBEBOP Event
↓
Outbound Cross-Dimensional Handshake
↓
Outside World
The two directions do not have to form a single workflow. Either direction can be used independently.
An inbound Cross-Dimensional Handshake allows supported information or actions from outside MINDBEBOP to enter the Mental Background Layer.
MindEvent is MINDBEBOP's inbound Cross-Dimensional Handshake. It provides a structured way for an outside event to initiate a supported experience in MINDBEBOP.
An outside system might use MindEvent in response to something that happened in the user's own environment or workflow. What the event represents is defined by the system or automation the user chooses to connect.
The important distinction is the boundary:
Outside World
→ MindEvent
→ MINDBEBOP
Ordinary movement between MINDBEBOP apps is not MindEvent and is not a Cross-Dimensional Handshake. It remains internal to the MINDBEBOP environment.
An outbound Cross-Dimensional Handshake allows supported MINDBEBOP events to be sent to an external HTTPS destination configured by the user.
MINDBEBOP announces the event. It does not decide what the outside world should do with it.
The external system might use that event to:
What happens after the event leaves MINDBEBOP is defined by the user and the external system they choose.
The current outbound Cross-Dimensional Handshake supports a small set of events that can reliably initiate an external HTTPS request when the event occurs.
Each event can be enabled or disabled by the user. An outbound destination must also be explicitly configured before MINDBEBOP attempts to send the event.
MINDBEBOP intentionally does not offer a Cross-Dimensional Handshake trigger simply because an internal event exists. An event is exposed only when the implementation can initiate the external handshake at the event itself under normal operation.
The central privacy rule for outbound Cross-Dimensional Handshake is simple:
Cross-Dimensional Handshake transmits events, not thoughts.
Outbound Cross-Dimensional Handshake does not transmit user-created text.
That means it does not send:
Depending on the event, an outbound handshake may contain limited technical event metadata such as:
These identifiers identify technical events or sessions. They do not contain the name, instructions, Mental Destination, or other text of the Mental Steps.
Cross-Dimensional Handshake is defined by crossing a boundary, not by communication alone.
MINDBEBOP app → MINDBEBOP app
Internal communication
Outside World → MINDBEBOP
Inbound Cross-Dimensional Handshake
MINDBEBOP → Outside World
Outbound Cross-Dimensional Handshake
For example, MindEntry opening MindBackOut during Mental Steps is not a Cross-Dimensional Handshake. MindBackOut returning to MindEntry is not one either. A thought moving between supported MINDBEBOP apps remains inside the MINDBEBOP environment.
The handshake begins only when the MINDBEBOP boundary itself is crossed.
The boundary is also a privacy boundary.
For outbound Cross-Dimensional Handshake, MINDBEBOP exposes the event without exposing the user-created thought content behind it.
An external system can therefore know that a supported event occurred without receiving the thought, Mental Destination, Mental Steps instructions, or other user-created text that may have existed inside MINDBEBOP.
The outside world can receive the event.
The thought can remain inside.
Inbound MindEvent works in the opposite direction: supported information or an action crosses from outside into the MINDBEBOP environment.
Cross-Dimensional Handshake is an architectural concept, not a single transport technology.
The current outbound implementation can send supported event metadata as an HTTPS request to a destination explicitly configured by the user.
MindEvent provides the inbound side of the architecture, allowing supported outside events to enter MINDBEBOP.
Other MINDBEBOP mechanisms — including local app-to-app handoffs, shared on-device storage, and internal navigation between MINDBEBOP apps — may help experiences continue inside the ecosystem, but those mechanisms are not themselves Cross-Dimensional Handshakes.
Future implementations may introduce additional inbound or outbound transports while preserving the same underlying distinction: the handshake exists at the boundary between MINDBEBOP and the outside world.
View the MindEvent API documentation →
MINDBEBOP does not need to become the system that controls everything around the user.
Instead, Cross-Dimensional Handshake provides a narrow boundary through which MINDBEBOP and user-chosen external systems can acknowledge one another.
A Mental Steps event can become meaningful outside MINDBEBOP without exporting the Mental Steps themselves. An outside event can enter MINDBEBOP without requiring the outside system to become part of the Mental Background OS.
The two systems remain independent. The handshake connects them only at the boundary.
Inside MINDBEBOP, thoughts can remain thoughts.
Across the boundary, events can travel.
That boundary is the Cross-Dimensional Handshake.
Copyright © 2026 MINDBEBOP — All rights reserved.