Director,

Requesting approval to begin production on the ELITE variant. Standard FLOATERs are performing well in patrol roles but their armor rating is insufficient for direct engagement with high-speed threats. The ELITE doubles hull plating and increases turret tracking speed by 40%.

Unit cost is 3x standard. I know the budget is tight. But if something gets past ground teams, these are the only thing between it and the sector boundary.

— Okoro

AUTOMATED INTRUSION DETECTION
THREAT LEVEL: UNKNOWN
LOCATION: SECTOR 0 / BLOCK A / ADDRESS 0x00
SIGNATURE: UNRECOGNIZED — OUTSIDE ALL KNOWN MALWARE TAXONOMIES
RESPONSE: PMC KILL TEAM ALPHA DISPATCHED

ALL PERSONNEL: MAINTAIN POSITIONS. DO NOT APPROACH SECTOR 0 WITHOUT AUTHORIZATION.

Alpha is gone. All six. Just got off the radio with their squad lead. Last thing he said was "He's too fast, rounds are going behind." Then the line went dead.

17 seconds from first contact to total loss.

Deploying Bravo and Charlie to Address 0x01. Requesting permission to activate the FLOATER network in Sector 0.

— Reznik

Director,

Telemetry from the Address 0x00 engagement is attached. Process trace results are abnormal.

The entity lacks an instruction pointer, stack, and heap allocation. It occupies memory the way a process does, but the scheduler is blind to it. Absent from all process tables. System monitoring reported idle state during the entire engagement.

It uses CPU time. It takes it directly. The request pipeline is bypassed.

Reclassifying from UNKNOWN to CLASS OMEGA.

— Ashworth

One of my ELITEs is destroyed. Gone. The explosion took out 12 ground personnel who were sheltering near it.

I'm reviewing the turret camera footage. The subject attached something to the ELITE — some kind of tether. It swung from the ELITE like a pendulum, used the momentum to reach the next address block, and the ELITE detonated on impact.

The turret tracking system was operating correctly. It had the subject locked. The subject was simply moving faster than the servos could physically rotate. The turret was always pointing at where the subject had been 0.3 seconds ago.

I have 19 ELITEs remaining. At this rate of loss, I'll have zero by end of day.

— Okoro

Director,

Flagging unusual filesystem activity by svc_backup. They created a hidden directory in /sys/firmware/memory_map/ and placed two files in it. One is an encrypted readme. The other is a Godot scene file describing some kind of grappling mechanism.

The directory permissions are set to 777 (world-readable, writable, executable). This is a violation of Architecture Division security policy.

svc_backup missed three consecutive check-in pings. Their process is absent from the scheduler.

Recommend immediate credential revocation and workstation quarantine.

— Automated Security Monitoring

Listen up.

Target moving above 550 u/s: hold fire. Take cover. Let it pass. Your rounds will land behind it. Every shot gives away your position for zero effect.

Target drops below 250: engage with everything. Full burst. That's your window.

Between 250 and 550: use your judgment. Some of you will land hits. Most will miss.

I'd rather have living soldiers who held fire than dead ones who emptied their magazines.

— Reznik

Director Voss,

Your request for emergency funding has been reviewed. The board has approved partial allocation — enough to fortify Sectors 2 and 3. Sector 1 fortification is deferred pending cost analysis. Sector 4 is not in scope at this time.

We note your recommendation to suspend containment operations against the designated threat. The board maintains that the situation remains recoverable. We expect continued effort.

Regards,
The Board of Directors
Containment Systems Ltd.

Director,

The subject crossed the Sector 1 boundary threshold 4 seconds ago. Sector 1 is breached.

During the crossing, an experimental scheduler left behind by ██████████ registered a detection event. ██████████ built this scheduler roughly 2,000 cycles ago, before leaving the company. It was decommissioned and left on a deprecated hardware partition. It was still running.

The scheduler detected the subject for 2 milliseconds as it passed through the boundary threshold. Two milliseconds. Every other monitoring tool in the system reports idle during the same window. This scheduler — running on architecture so old it predates the current process table format — saw it.

The detection log confirms the subject is software-based. It runs on the same fundamental instruction set as every other process in this system. It follows the same clock. It uses the same memory bus. For 2 milliseconds, it was visible to a scheduler that was designed before our current containment architecture existed.

What this tells us:

1. The subject is a process. It has a footprint. It can be observed.
2. Our current monitoring tools are blind to it because they were built after the subject learned to hide from them. The old scheduler worked because the subject has never encountered it.
3. The subject's root process — wherever it actually lives in memory — is somewhere in this system. It entered from outside, but it is here now. Somewhere in the address space, there is a PID we are missing.

I am requesting immediate access to all deprecated hardware partitions across Sectors 1 through 4. If ██████████ left one scheduler running, there may be others. If we can find more observation windows the subject hasn't adapted to, we can start building a map of where it goes when it disappears between engagements.

The 2-millisecond detection window will shrink. The subject adapts to everything. We need to move on this before it finds the old scheduler and eats it too.

— Ashworth