The Red Triangle

Act I — Anomaly 47-Alpha

The audit took four minutes and twelve seconds. Standard procedure: open Citizen Memory File 44721, run integrity scan, flag and optimize any anomalies, close file. Eli Reed performed it with the mechanical precision of a man who had done it seventeen thousand times.

The scan returned clean. Standard result. Standard day.

Except for the red triangle.

Eli saw it in the periphery of the audit display—a small red triangle, exactly three millimetres at the base, hovering at memory sector 7-Gamma. It was not part of the standard flag system. The Union's flag system used colours: blue for minor inconsistencies, yellow for moderate concerns, red for critical anomalies. But the red triangle was different. It was geometric, precise, and it pulsed at a frequency that made Eli's eyes water.

He ran a second scan. The red triangle remained.

He ran a diagnostic. The system reported nominal.

He ran a third scan, manually this time, overriding the automatic optimization protocol. The red triangle remained.

Eli flagged the file for supervisor review, which was not standard procedure for a level-three auditor, but he was not a man who ignored anomalies. It was, after all, what he was paid to do. His job description—Citizen Memory Integrity Auditor, Grade III—required him to identify, categorize, and optimize cognitive irregularities in citizen memory files. He was good at his job. The union rewarded competence with stability, and stability was the highest virtue in a society that had eliminated war, poverty, and crime.

The supervisor's response came three hours later: "Anomaly noted. Optimized in next maintenance cycle. Do not re-audit."

Eli closed the file. But the red triangle was now inside his own head, and he could not optimize it out.