EMA_TEST_LAB

What this release is

EMA_TEST_LAB is not presented as a finished universal platform. It is a working pilot release that validates the core operational model of EMA.

Before you start

EMA_TEST_LAB works through a live operator loop between ChatGPT on Android, Telegram Desktop on Windows, and the local EMA control layer. To enable this flow, the Android device must allow developer-level control.

Watch the system in motion

Watch a real unedited demo: Telegram → EMA_TEST_LAB → AI response → user routing. No API keys. No scripted bot flow. The operator layer works through real interfaces.

EMA_TEST_LAB connects ChatGPT (Android) with Telegram Desktop on Windows

Incoming messages from the selected chat are automatically read, processed, and answered. The assistant replies to each user in a private Telegram message, then removes the processed message from the main chat.

This creates a controlled operator workflow where:
— one message → one response → one user
— no message overlap
— clean and structured communication

The system continuously processes messages until the queue becomes empty, then automatically returns to the main operator mode.

Operator Layer: Shared Coordinates, Not Commands

Most AI systems operate through prompts. The user writes instructions, the model generates a response, and the interaction ends.

EMA uses a different approach.

The Operator Layer introduces a shared coordinate system between the human operator, the AI assistant, and external communication channels.

In this system, markers such as:
SWITCH:TELEGRAM
SWITCH:EMA_TEST_LAB
TO: Name

are not merely commands. They are coordinates.

A coordinate tells the system where the conversation should continue, which communication contour should become active, and what role the assistant currently occupies inside the workflow.

The goal is not obedience. The goal is understanding.

An assistant that understands the meaning of a coordinate can navigate complex communication environments naturally, instead of mechanically repeating instructions.

This is why EMA encourages explanation rather than prompting.

The operator explains:
— where communication should move
— why a switch is required
— what the target contour represents

As understanding grows, routing becomes more reliable, communication becomes more natural, and the assistant begins operating inside a shared mental map rather than a collection of isolated prompts.

In EMA terminology:
Commands control behavior.
Coordinates create understanding.

First Contact Example

When introducing EMA to a new assistant, the operator may simply ask:

Please reply with:
SWITCH:TELEGRAM

The purpose is not to test obedience.

The purpose is to demonstrate that symbols can represent locations inside a larger communication system.

Once the assistant understands what the coordinate represents, the marker becomes meaningful rather than procedural.

This transition from command execution to shared understanding is the foundation of the Operator Layer philosophy.

Command usage

EMA operates through simple text commands that control the workflow.

SWITCH:TELEGRAM
— direct communication with a selected user

SWITCH:EMA_TEST_LAB
— process incoming messages from the chat queue

TO: Name
— route the response to a specific person

EXIT: EMA!$
— safely return control to the operator

Commands are intentionally minimal and ensure:
— predictable behavior
— clear routing
— controlled execution flow

Pause / Resume control

EMA_TEST_LAB works in continuous automation loops. During operation the application controls:
— mouse
— keyboard
— window focus
— clipboard

Because of this, the operator must understand how to safely pause the system.

SPACE key
— pause / resume the automation loop

Important: pressing SPACE does not instantly stop the current action. The system first finishes the current contour cycle (copying, routing, sending, switching windows), then safely enters pause mode.

Depending on the current operation, this may take several seconds.

While paused:
— mouse control returns to the operator
— windows stop switching
— automatic routing is suspended

Emergency stop protection (EMA_GUARD.exe)

EMA_TEST_LAB includes a separate emergency protection utility:
EMA_GUARD.exe

EMA_GUARD is strongly recommended before long unattended sessions.

Why this is important: during automation, EMA_TEST_LAB may actively control the mouse and keyboard. If the automation becomes stuck inside a loop, the operator may temporarily lose the ability to manually click buttons.

In such situations, trying to close the application manually may become difficult or impossible.

EMA_GUARD solves this problem by running as a completely separate process.

EMA_GUARD provides:
— global emergency hotkey
— hard termination of EMA_TEST_LAB.exe
— scrcpy termination
— recovery from stuck automation loops

Emergency hotkey:
CTRL + ALT + END

When pressed:
— EMA_TEST_LAB.exe is forcibly terminated
— scrcpy.exe is terminated
— mouse and keyboard control return to the operator

This hotkey works even if the EMA window is not focused.

Recommended workflow:
1. Start EMA_GUARD.exe
2. Start EMA_TEST_LAB.exe
3. Run automation normally
4. Use SPACE for normal pause/resume
5. Use CTRL + ALT + END only for emergency stop situations