The Anomaly Manual

Chapter 4 - The Apartment on Ashford

Chapter 4 · 1,521 words

The deployment order arrived on a Tuesday. Ellis was at his desk, reviewing the phone booth anomaly's follow-up data. The prior recorder's measurements were inconsistent, the spatial extent varying by nearly a meter between observation sessions, which suggested either instrument error or an anomaly that was genuinely changing. The order appeared in his queue.

*Field Recorder Vey, Ellis. Assignment: Field Team 7, Team Leader Holt, Maren. Deployment: Ashford Street residential anomaly, third-floor spatial loop. Report to staging facility, Wednesday, 0600.*

He read it twice. Team 7 was Maren Holt's unit. He knew the name. Everyone in the field operations division knew the name. Maren Holt had been a Field Team Leader for eleven years. She'd lost entire teams to anomalies she couldn't decode in time, and she'd brought other teams home intact. The Bureau didn't publish those numbers, but the field operations division was small enough that reputation traveled.

The anomaly was a spatial loop. Third floor of an apartment building on Ashford Street. The loop repeated every forty-seven minutes: the same hallway, the same doors, the same lighting, cycling on a fixed interval. Prior observation teams had confirmed the loop's parameters and established that it was contained to the third-floor residential corridor. No casualties. No cognitive effects reported. A straightforward spatial anomaly.

Ellis opened the anomaly file.

The existing reports were from two prior observation deployments. Both were standard, one page each, maybe two with the supplementary data. The loop's interval was consistent. The spatial extent was stable. No secondary effects detected. The recommendation was for a containment assessment, which meant a containment team would be deployed after the observation phase confirmed there were no surprises.

Ellis read both reports. Then he opened the Bureau's accessible database and searched for *spatial loop*.

The search returned forty-three results. Not all were relevant. Some were temporal loops, some were spatial folds, some were recursive geometries that only technically qualified as loops. He filtered for *spatial loop, residential, fixed interval* and got eleven results.

He began reading.

Each report was a window into a different building, a different loop, a different team's experience of walking through a space that repeated. The intervals varied: twenty-three minutes, forty-seven minutes, one that ran on a sixty-one-minute cycle that no one could explain. The spatial configurations were different: hallways, stairwells, entire apartment units that folded back on themselves. But the underlying structure was the same: a space that repeated, a cycle that reset, a boundary that could be crossed but not exited.

Ellis read for two hours. He took notes in his own notebook, not the Bureau's digital system, which logged everything and could be audited, but the physical notebook that lived in his kit and went home with him every night.

He wrote down the intervals. He wrote down the spatial configurations. He wrote down the secondary effects that had been reported in some loops but not others: temperature fluctuations, auditory phenomena, in one case a faint smell of ozone that appeared at the loop's reset point and then vanished. He wrote down the containment outcomes: successful, failed, ongoing, abandoned.

He looked for patterns.

The loops destabilized. Not all of them. Four of the eleven had been contained without incident. But the ones that destabilized shared a characteristic: they had all been observed for multiple cycles before containment was attempted. The longer the observation phase, the higher the probability of destabilization. The correlation wasn't perfect, but it was there, a trend line that rose slowly and then steepened.

He wrote that down. *Extended observation correlates with loop destabilization. Causation unclear — does observation cause destabilization, or do unstable loops attract longer observation?*

He didn't have an answer. He had the question, and the data, and the trend line. That was enough for now.

He kept reading.

The apartment building on Ashford Street was a four-story brick structure built in the nineteen-sixties. The third floor had four apartment units and a central hallway. The loop encompassed the entire floor, the hallway and all four units, and repeated every forty-seven minutes. The reset was clean: one moment the corridor was at minute forty-six, the next moment it was at minute zero, with no visible transition.

The prior observation teams had not reported any secondary effects. No temperature fluctuations, no auditory phenomena, no cognitive contact. A clean spatial loop.

Ellis had read eleven reports on spatial loops. He knew what clean spatial loops looked like in the data. He also knew that three of the eleven loops he'd reviewed had started clean and then developed secondary effects in the third or fourth observation cycle.

He closed the database. He reviewed his notes.

The loop on Ashford Street had been observed for two prior deployments, a total of approximately six cycles. If the destabilization trend held, the probability of secondary effects emerging in the next cycle was not negligible.

He wrote that in his notebook too. *Prior observation: ~6 cycles. Risk of secondary effects: non-negligible based on historical pattern. Prepare documentation framework for cognitive, temporal, and environmental secondary effects in addition to spatial loop parameters.*

He wasn't preparing because he expected to be important. He was preparing because incomplete documentation felt like a kind of lying. Not to anyone else, but to the record itself. If the anomaly escalated and he hadn't built a framework for capturing the escalation, his documentation would be reactive instead of comprehensive, and reactive documentation missed the transitions that mattered.

He also wasn't preparing because anyone had asked him to. No one on Maren Holt's team knew he'd spent two hours reading historical spatial-loop reports. No one would review his notes. No one would evaluate his preparation. He was doing it because the work was the work, and doing it badly when he could do it well was a choice he wasn't willing to make.

Ellis closed his notebook. He put it in his kit alongside the measuring tape, the stopwatch, and the Pilot G-2. He zipped the kit and set it by the door.

It was seven o'clock. He had eleven hours before he needed to be at the staging facility.

He lay on his bed and stared at the ceiling and thought about spatial loops.

---

Maren Holt's office was on the second floor of the field operations building. It was small: a desk, two chairs, a whiteboard covered in deployment schedules written in red marker. The door was open.

Ellis stood in the doorway. He had his deployment order in his hand.

"Vey." Maren didn't look up from her screen. "Come in."

He stepped inside. The chair facing the desk was vinyl, cracked at the seams. He sat.

Maren finished whatever she was reading, then turned. She was in her fifties, maybe older. The kind of face that didn't reveal age easily because it had spent too much time in difficult environments. Her hair was short and gray. Her hands were flat on the desk, still, the way a commander's hands were still when she was assessing you.

"I read your file." She said it without preamble. "The report from Linden Avenue. The transformation sequence."

Ellis said nothing.

"Your measurements were thorough." She paused. "More thorough than I'm used to from a recorder."

"The data was there."

"The data is always there. Most people don't write it down." She leaned back. The chair creaked. "You know what this deployment is?"

"Spatial loop. Third floor, Ashford Street. Forty-seven-minute cycle. Two prior observation deployments, no secondary effects reported."

"That's the brief." She watched him. "That's not what I'm asking."

Ellis considered the question. *That's not what I'm asking*. She was asking what he thought, not what he'd been told.

"I reviewed the historical spatial-loop reports in the database. Eleven comparable cases. Three developed secondary effects after multiple observation cycles. The correlation between observation duration and destabilization isn't conclusive, but it's present."

Maren's expression didn't change. Her hands didn't move.

"You did that on your own time."

"Yes."

"You're a recorder. Your job is to document what's in front of you, not to predict what might happen."

"I know."

Another pause. The whiteboard behind her had a deployment schedule for the next two weeks. Ellis could see his own name on it, or rather, the designation *REC* next to the Ashford Street entry. Recorder. The lowest rank on the team sheet.

"Be at the staging facility at zero six hundred," Maren said. "Don't be late."

"I won't."

He stood. He was at the door when she spoke again.

"Vey."

He turned.

"Whatever you think you saw in those historical reports, we're going in to observe. Not to contain. Not to predict. You document what's there. If it's a clean loop, you document a clean loop. Understood?"

"Understood."

He left. The door closed behind him.

Maren Holt sat in her office and looked at his file on her screen. The transformation report from Linden Avenue. Seven pages. The kind of documentation that made an analyst's eye catch and hold.

She closed the file. She had a deployment to plan.