MINTCAKE SYSTEMS // BOOT SEQUENCE INITIATED
> LOADING KERNEL...[OK]
> MOUNTING SECURE PARTITION...[OK]
> DECRYPTING COMMS ARRAY...[OK]
> ESTABLISHING FIELD CONNECTION...[OK]
> SCANNING FOR HOSTILES...[CLEAR]
> SYSTEM ONLINE
> STAND BY FOR TRANSMISSION
// CLICK ANYWHERE TO SKIP
< Back to transmissions
⚠ SIGNAL PARTIALLY DEGRADED ⚠
TOP SECRET
EYES
ONLY
// CLASSIFICATION: UMBRA-7 — UNAUTHORISED ACCESS IS A CRIMINAL OFFENCE //
ORIGIN: ENCRYPTED — SOURCE UNKNOWN
DATE: 01 / 04 / 2026
CLEARANCE: SIGMA BLACK
STATUS
PARTIAL RECOVER
INTEGRITY
84% RECOVERED
PRIORITY
ELEVATED
TYPE
FIELD REPORT
// TRANSMISSION SUBJECT
FIELD REPORT // NAMED PERSONNEL — FIRST CASUALTIES CONFIRMED
DEVELOPMENT

⚠ TRANSMISSION PARTIALLY DEGRADED — SOME DATA BLOCKS IRRECOVERABLE — ⚠

// TRANSMISSION STATUS

RELAY: RECOVERED ARCHIVE
ENCRYPTION: DEGRADED
DATA INTEGRITY: 84% RECOVERED

— PARTIAL RECONSTRUCTION FROM FRAGMENTED OPERATIONAL LOGS —

// OPERATIONAL ASSESSMENT

Before this operation, two systems existed in parallel.

A base. A battlefield. Neither knew the other was there.

The base maintained a roster — named personnel, hired and trained, accumulating history. Kill counts on record. Roles assigned. Faces known to their commander. The battlefield had a grid and five units. Anonymous. Interchangeable. Disposable in the way that placeholder things are disposable — because nothing about them was real.

When a mission ended, you returned to base. Nothing had changed. Nobody was missing. The economy was unchanged. The roster looked exactly as you had left it.

The two systems were separate games running in the same project.

// WHAT CHANGED

A lightweight command relay was built between the layers. Its function was simple and its implications were not: carry the soldiers you selected in base management into the tactical layer, and carry the consequences back.

Outbound: selected personnel were written into the relay before the level transition. The tactical layer read from it on startup. Named soldiers spawned at their positions — not placeholders. The people you had sent.

Inbound: when those soldiers died, a result was assembled. Victory state. Credits. The unique identifiers of the personnel who did not survive. That result was written back through the relay on mission end. The base read it. Applied it. Recorded it.

// FIELD OBSERVATION — RECOVERED LOG FRAGMENT
Soldiers selected from active roster. Named. Their records on file.

Level transition. Tactical map loaded.

They were there. The names matched. The stats matched. The soldiers you sent were the soldiers who arrived.

The mission ran.

Some of them died.

At the result screen: casualty designations listed. On return to base: roster updated. KIA flagged — not deleted, not reset. Permanent record. Gone from active duty.

The base knew. The campaign knew.

Credits applied. The economy reflected what had happened in the field.
// ANALYST NOTE

The significance of this operation was not technical. It was consequential.

Before: you could run both systems indefinitely. They would never affect each other. The soldiers in your base had no relationship to the units on the battlefield.

After: the roster you were looking at in base management was the same roster that mattered on the battlefield. A soldier with twelve kills built over previous operations could walk into a bad engagement and not come back. Permanently.

The game stopped being two systems. It became one thing.

// ADDENDUM — CLASSIFICATION NOTE

Analysts note that the question of whether this consequence model could survive a more complex operational boundary — one neither layer could directly see — remained unresolved at the time of this transmission.

That question has since been answered. See: REVOLVE.

⚠ THIS DOCUMENT WILL SELF DESTRUCT ⚠
DOC-ID: MCG-TX-FIELD / REV.█