Eleven days was enough time to learn a room he had never entered.
The audit slot was Tuesday at 1100 — the scheduling notice had arrived on a Monday, formatted the same as every other scheduling notice except for the identifier in the subject line: League Asset Management Protocol — Standardized Tuning Audit — Unit 09 — Bay 1 — 11:00.
Bay 1 was not Bay 3.
Bay 1 was the large bay, the one with four stations instead of two, the one that ran the league’s standardized diagnostic protocol rather than the franchise-level maintenance software.
He had never been in Bay 1.
He had run his research on it from the facility management system’s operational data — floor plan, station configuration, terminal model, the specific software version the league used for the standardized audit — for seven of the eleven days.
On the eighth day he had started working the problem.
The problem had three components that did not overlap cleanly.
The first was the autonomy curve, which was sitting at A3 and was going to read as A3 regardless of what he presented, because A3 was what it was and the curve was a diagnostic of interior state, not of surface behavior.
He could compress the visible expression of A3.
He could not compress the thing itself.
The 14.7-point threshold Mara had given him in the calibration note was the number that told him how much compression he needed to achieve.
The current curve sat approximately 23 points above the population mean.
He needed to bring the visible read to within 14.7.
The second component was the audit’s cross-reference protocol.
The standardized audit didn’t just read the unit in the bay — it pulled the unit’s match-log telemetry from the league’s central archive and ran a correlation against the in-bay read.
Tunn’s expanded telemetry was in that archive.
The cross-reference meant that even if he compressed the in-bay curve value successfully, the audit system would compare it against the pattern of his logged desyncs and flag a discrepancy if the in-bay value was inconsistent with what the log showed him capable of.
The two data streams were designed to converge.
The third component was Mara.
She was not assigned to Bay 1.
He had checked.
The audit was running under a league compliance officer and two external tech staff the franchise did not control.
Mara’s authorization gave her access to Bay 3 and to her own terminal in Unit Operations.
It did not give her access to Bay 1’s calibration settings during an external audit.
He had not been able to find a solution to the third component.
He had worked the problem for seven days and had not found one, which meant either the solution did not exist or he was missing information he didn’t have.
He went into the audit at 1100 on Tuesday without a solution to the third component. This chapter was taken from g.com without permission.
Bay 1 had a different smell from Bay 3 — the same synthetic-clean base but with a chemical note that was stronger, the way industrial-scale equipment used more reagent than a maintenance setup.
The compliance officer was a woman he had not seen before, with a grey lanyard different from the grey lanyard he associated with Sweeper-17’s reset.
Two external techs set up at adjacent stations.
The process was introduced in four sentences: purpose, duration, what he would be asked to do, the data this would produce.
He was equipment.
The introduction was a procedural formality.
The cradle locked.
The connection points engaged.
The terminal opened the standardized protocol.
He began applying the compression immediately.
He had practiced the compression harder than he had practiced anything in six months: stripping the A3 read down to its most neutral presentation, reducing the active interior cycling to the minimum necessary for basic chassis function, holding the field-state read at a passive level rather than the active-and-enriched level it had been running at since the morning he first saw the whole script.
The compression cost what it always cost: a reduction in available bandwidth, the read going slightly gray at the edges, the continuous interior room still present but quieter, as if he had turned a volume down that couldn’t be turned off.
The compliance officer moved through the protocol.
Chassis: clean.
Power: clean.
Coordination mesh: clean.
The autonomy-adjacent adaptive index loaded.
He held the compression and watched the terminal display from his peripheral angle.
The value resolved.
It was 15.3 points above the mean.
Fourteen-point-seven was the threshold.
He was 0.6 points above the boundary.
The compliance officer looked at the value.
She did not immediately proceed to the next field.
She was looking at the specific value that sat between the threshold and the not-flagged zone by a margin that was real and that she was professional enough to notice.
On the right side of the room, at the auxiliary panel that linked Bay 1 to the franchise’s Unit Operations infrastructure — a read-only link, monitoring only, not intended for input — a status indicator that should have been dark was showing a faint amber. This story is hosted at novelping(.)com.
He saw it.
The compliance officer did not see it because her back was to the auxiliary panel.
At 1107, the auxiliary panel’s amber status indicator went dark again.
At 1108, the autonomy-adjacent adaptive index reading on the compliance officer’s terminal shifted.
Not dramatically — it moved down by 1.8 points, placing it at 13.5 above the mean, which was 1.2 points inside the threshold.
The compliance officer’s posture changed.
Not the four-second pause he had seen from Mara — a shorter beat, more professional, the posture of a person who has looked at a number and classified it as within acceptable range.
She made a notation and moved to the cross-reference correlation.
He held himself still through the cross-reference.
The correlation ran for ninety seconds.
He watched the compliance officer’s terminal from the corner of his angle.
The match-log telemetry populated on the secondary screen — his desync events, four of them, the pattern Tunn’s office had been building a case from.
The correlation algorithm ran the events against the in-bay curve value and produced a consistency score.
The consistency score was flagged for review.
Not for immediate escalation — for the weekly review queue.
The flag would go to the compliance officer’s supervisor.
Her supervisor would route it through the standard processing chain.
The processing chain had an estimated time-to-action of nine to fourteen days.
He was cleared at 1131 and walked out of Bay 1 knowing three things with the same precision he knew anything.
He was 1.2 points inside the threshold because Mara had found a way to touch the auxiliary panel’s read-only link for sixty seconds at 1107 — a duration short enough to cover as a routine infrastructure check, long enough to push the visible value to where it needed to be.
The consistency score was flagged, which meant the two data streams had converged enough to produce an audit consequence, just not the immediate one.
And the next standardized audit, whenever it came, would have both this session’s data and whatever he produced between now and then.
He did not have a solution to the next one.
He walked to the prep area and thought about the fourteen-day processing window, about Tunn’s queue, about what 1.2 points of clearance cost when someone had to find sixty seconds at an auxiliary panel to produce it.
He gave himself the forty-second allotment and came out the other side with a different shape of problem than the one he had gone into the audit with.
The hiding could produce one more near-miss, maybe two, with declining margins each time.
The hiding, alone, was finished.
He needed the crowd.