May Be Cited

The morning after the courtyard encounter with Sable, the waiting period settled in hard. With the External Assessment outcome filed and two of the three working days until its delivery already gone, I needed something to occupy the time between. The AFFINITY INTERACTION DYNAMICS subsection ran to forty-seven pages of indexed documentation, and by the third reading session I'd stopped following it in order.

That approach made more sense than following the document start to finish. Index to cross-reference, cross-reference to footnote, footnote to a worked example buried four sections back that illustrated the principle better than the section written to explain it. I'd marked the page order in the margin with small numbers, a trail through the document as it actually worked versus how it claimed to work. The page in front of me now was twenty-three, and I'd reached it from thirty-one.

The afternoon was quiet. The hall doors had stayed shut since morning, and the courtyard held its particular midday stillness, stone holding the heat, the covered walkway throwing a stripe of shade that moved too slowly to track. My interface sat propped against my knee. The physical copy of the route guide was open beside it.

Nadia had gone back to her hall after lunch. The others trickled out by midday, and I'd stayed because the bench was close enough to an administrative notice board posted near the Annex entry that I could read any updates without crossing the courtyard. Nothing had posted yet.

The processing office opened at seventh bell tomorrow. I had time, which was not the same as having useful time.

Page twenty-three described what the documentation called differential compound interaction, the behavior of multiple secondary affinities when a primary affinity is either absent or operating in a suppressed state. The language was cautious in the way documentation language gets cautious when the writers hadn't wanted to commit to a mechanism.

The worked example on page thirty-one had been clearer: a candidate with a light primary and two secondary affinities routed through fire and force had produced interaction patterns where the secondary affinities reinforced each other when the primary was actively suppressed during a test configuration. The documentation framed this as a known edge case. The footnote attached to that section noted the behavior hadn't reproduced under standard protocols.

I'd underlined the word "standard" and written a small question mark beside it. Standard protocols were built for candidates who came through attunement with a functional primary. The whole framework assumed continuity between the primary and secondary layers. When that continuity was absent, the documentation didn't predict failure. It just stopped predicting.

That was the pattern I kept finding. The documentation described what happened under normal conditions with exhausting precision and then went quiet at exactly the point where my configuration diverged.

Page forty-one, which I'd reached earlier from page twelve, had a table listing observed interaction types sorted by primary affinity category. Twelve rows, four columns. The last row bore the label COMPOUND NON-STANDARD and contained three cells filled with data and one that read "SEE BOARD DOCUMENTATION." I'd seen that phrase four times in four different sections, and across the courtyard, the notice board remained empty.

Footsteps came from the covered walkway, and I knew them as Wynn's before he cleared the corner, that particular stride with a slight pause on the longer step. He had his interface in his hand rather than his wrist mount, which meant he wasn't actively annotating. He came over and sat at the far end of the bench without asking whether I wanted company. He just sat, which was accurate enough as a read that I didn't mind.

He glanced at the route guide open beside me. "Theory module or documentation?"

"Route guide cross-referenced against the theory module," I said. "The route guide index is better organized."

"I noticed that too." He set his interface face-down on his knee. "The theory module writers assumed the reader would start at section one and proceed forward. Nobody actually reads documentation that way."

"Forty-seven pages into the affinity interaction section," I said, "and the best explanation of compound secondary behavior is in a footnote on page thirty-one. The section that's supposed to explain it is pages three through eight."

"What does the footnote say?"

"That the behavior hasn't reproduced under standard protocols." I showed him the margin note and the underlined word. He looked at it, then nodded once, which meant he'd arrived at the same interpretation without needing it explained.

We sat. The shade stripe from the covered walkway had moved maybe two handwidths since morning. Wynn picked up his interface, opened it, closed it, set it back down. There was something he wasn't ready to say yet, which was interesting because Wynn generally said things when he was ready.

"The formal inquiry," he said finally. "Are you going to the processing office tomorrow?"

"Seventh bell," I said.

"I was thinking the same." He turned his interface over. "Petra as well, probably. The three of us submitting through the same window gets us one consolidated response under the standard documentation, which may be faster than three separate ones."

That was a reasonable reading of how Annex administrative processes worked, and also a reading I hadn't confirmed anywhere in the documentation. "Does it say that?"

"The route guide doesn't say it. The theory module doesn't either." He paused. "It's structural inference from the way the standard protocols handle non-standard classifications. When a classification requires board coordination, the processing office consolidates related inquiries before routing them up."

"You're inferring the consolidation step from the general protocol structure."

"Yes."

The inference was plausible. It might also be wrong, in which case three separate inquiries would generate three separate tracking numbers that reached the board as independent items, with different timeline implications than one consolidated item. "I'll go at seventh bell," I said. "What you do at seventh bell is your own business."

Wynn almost smiled. "That's a reasonable position."

"It's also an accurate one."

He picked up his interface again and this time actually started working. I went back to page twenty-three. The shade stripe moved another finger-width, then held still the way anything holds still when you watch it too closely.

Seventh bell the next morning was a thin sound, two short strikes from somewhere behind the main Annex building where the administrative wing sat separate from the training halls. I'd been up since before sixth, which was not unusual. The interface had pushed two new notifications overnight, both marked LOW PRIORITY: one confirming the cohort session agenda would post within twenty-four hours, one confirming my inquiry submission window was open.

The processing office sat in the administrative wing, past the corridor that branched off the main Annex entry. A plain door, no marker on the lintel, held a printed card in a metal bracket reading PROCESSING: ADMINISTRATIVE HOURS ONLY, the font too wide for the slot, its corners curled. By the time I reached it, the door was already open.

Wynn was inside, standing at a low counter that divided the room. Across from him was a woman in her mid-forties with a short gray streak through otherwise brown hair, sitting on a stool with a physical ledger open in front of her and a secondary interface mounted on an adjustable arm to her left. The interface showed a candidate roster, and she was looking at it when I came in.

She glanced up. "Second inquiry?"

"Eli Falken," I said. "Restricted classification, deferred attunement, Arch-Tier cohort."

She wrote the name in the ledger. Her handwriting was small and even, cramped by habit into narrow columns. "Inquiry type?"

"Board coordination timeline for non-standard classification. Specifically whether the processing office can confirm a coordination date or a date range for when the board will convene on deferred Arch-Tier cases from this cohort's intake."

She wrote that too, summarized into something shorter. I watched the pen move and waited.

"You're the second," she said, without looking up.

"I know."

Wynn had been watching the exchange from the side, wrists resting on the counter, interface off. He wasn't annotating. He was just there, visible enough that the administrator registered he was paying attention, close enough to hear anything she offered, far enough back to let the transaction proceed without his involvement.

The administrator finished writing. "Third inquiry from this cohort?"

"Petra," Wynn said. "Same classification type."

"She submitting separately?"

"I don't know," he said.

The administrator's pen hovered over the ledger. She made a note in the margin of the row she'd just written, tapped something on the mounted interface, and looked back. "Standard processing time for this inquiry type is three to seven administrative days for an initial response. If the board has already set a coordination date, the response comes faster. If they haven't, the response will confirm that a date is pending and give you the inquiry tracking number." She paused. "The tracking number lets you submit a status request after five administrative days if no response has come."

"Is there a way to indicate priority," I asked, "given the cohort session calendar."

Her answer came flat and unhurried, the words worn smooth from being said too many times before. "Priority designation requires supervisor approval. I can note the cohort session timing in the inquiry record, and that notation goes with the file to the board coordinator. Whether it affects scheduling is at the board coordinator's discretion."

"Please note it," I said.

She did. Another three lines of small even text.

When she was done she tore two slips from a pad on the counter. Each had a tracking number printed on it and a handwritten line below. She handed one to Wynn and one to me. Mine read: INQUIRY REF 7-1142, COHORT SESSION NOTATION INCLUDED, EST RESPONSE 3-7 ADMIN DAYS.

"Administrative days," she said, "the Annex calendar marks in the main corridor. Not every day is an administrative day. Count from today."

I folded the slip and put it in my interface case. Wynn looked at his and slid it inside the annotated courtyard map he'd been carrying. The administrator had already turned back to her mounted interface.

Outside, the corridor had more traffic than when I'd arrived: two people I didn't recognize from any cohort moving toward the main entry, a coordinator I'd seen twice before carrying a stack of physical files, a candidate from the other wing whose name I hadn't learned yet. The Annex ran on its own schedule, and the administrative morning was clearly a different rhythm from the training morning.

Petra was coming down the corridor from the main entry. She had her interface in her hand and was moving at a pace that suggested she'd checked the time recently.

"Office is open," Wynn said.

"I know," she said. "I went to the wrong wing first." She looked at the door, then at us. "You both submitted?"

"Yes," I said.

She went in. We waited in the corridor, not for any particular reason, only that leaving immediately would mean walking away from information if the administrator said anything different to Petra than she'd said to us. Two minutes later Petra came back out holding a tracking slip.

"Three to seven administrative days," she said.

"With cohort session notation," I said.

"She offered that without my asking." Petra looked at the slip, then put it in her jacket pocket. "So she's done this before. This specific situation."

That was a reasonable inference. The card format was pre-printed. The ledger had existing rows in the same format above the one she'd filled in for Wynn. The inquiry type was apparently a known category.

"There were previous cohorts," Wynn said. "Non-standard classifications are uncommon, not unprecedented."

"Which means someone got an answer before," Petra said. "Which means the board has a process for this."

None of us said what followed from that, which was that having a process didn't mean the process produced the outcome any particular candidate needed. I put the thought where it belonged and left it there.

Back in the courtyard by eighth bell, the morning had shifted. The lintel markers on two of the hall doors were lit, which meant Fass and Coll were inside running modules. Nadia was on the bench across from mine with her physical route guide open and her interface running beside it, the same configuration she'd used during the courtyard discussion the previous day. Renne was nowhere visible.

Nadia looked up when the three of us came through the walkway entrance. Her eyes dropped to the tracking slip in my hand.

"Processing office," I said, because the slip was visible.

"Seventh bell," she said. "Three to seven days?"

"With the cohort session notation."

She nodded and looked back at her route guide. After a moment: "The cohort session agenda posted at seventh bell. It's in the shared queue."

I opened my interface. The agenda notification sat at the top of the cohort channel, posted seven minutes ago. The first cohort session covered three topics: attunement architecture review, primary-secondary interaction foundations, and system interface calibration for registered affinities. The last item had a footnote. It read: CANDIDATES WITH RESTRICTED INTERFACE ACCESS OR DEFERRED ATTUNEMENT STATUS WILL RECEIVE MODIFIED SESSION MATERIALS. SEE SECTION 4B.

Section 4B ran three paragraphs thick. It described a parallel track for restricted candidates: theory review covering the same conceptual material as the calibration modules, without live affinity activation. The parallel track would hold in the same room at the same time as the main session. Participation was mandatory. The system would track performance individually.

That last part I'd already known from what Petra had found in the theory module index two days ago, but seeing it in the official session agenda made it concrete in a different way. The third paragraph noted that a candidate could cite satisfactory completion of the parallel track as supporting documentation in a non-standard attunement case. I read that sentence again.

Wynn was already on the same passage, judging by the angle of his interface. He hadn't said anything.

"Section 4B," I said.

"Third paragraph," he said.

Petra, her attention fully on her screen, said, "The board may cite it as supporting documentation. Not 'will consider.' Not 'shall take into account.' May cite. Discretionary language."

"But it's a mechanism," I said. "The session feeds into the board file."

"If completion is satisfactory," Wynn said.

Nadia was reading the agenda now too, her route guide closed beside her. "Whatever 'satisfactory' means in this context, the session is now something that actively affects your board file rather than running parallel to it."

"The definition of satisfactory isn't in section 4B," I said.

"No," she said. "But the session materials will have their own criteria. That's standard for theory modules with performance tracking."

Across the courtyard, the door to the far left hall opened and Renne came out, blinking. She pulled the door mostly closed behind her, checked the lintel marker as a reflex, found it still active, and let it settle. She crossed the courtyard and dropped onto the bench beside Nadia without ceremony.

"Section 4B?" she said, looking at my interface.

"The cohort session agenda," Nadia said.

"Third paragraph," Renne said. "I saw it ten minutes ago. Satisfactory completion as supporting documentation. The language is interesting."

"Interesting how," I said.

"It says the board may cite it. Not 'will cite.' Not 'shall consider.' May cite." She stretched her legs out in front of her. "The board has discretion about whether to use it, but the mechanism exists for them to use it if they want to. That's different from it not existing at all."

That was a precise reading. I'd parsed it similarly but she'd named the distinction faster. "You read contract language," I said.

"Route documents back home have a lot of may versus shall distinctions. You learn to care about them." She looked at her own interface. "The main session materials also include a note about the system waiving the calibration component for restricted candidates and replacing it with a conceptual mapping exercise. I don't know what that means in this context."

"Neither do I," I said.

"The modified materials probably define it," Wynn said. "They'll post before the session."

Renne accepted that and opened a new section in her interface, slouching back against the bench like someone with nowhere else to be.

Two new items sat in my queue, unopened, both marked as additions to my INTERIM TRAINING ACCESS (LIMITED). The first was a new module: COHORT SESSION PREPARATION: PARALLEL TRACK OVERVIEW. The second was labeled CONCEPTUAL MAPPING EXERCISE: ORIENTATION MATERIALS. Both had posted at seventh bell with the agenda.

I looked at the tracking slip sitting in my interface case. Three to seven administrative days, cohort session notation included. The session itself was in two days. If the board response came at the early end of the window, there might be overlap. If it came at the late end, the session would finish before any board response arrived.

The parallel track materials were already in my queue. The board file was building on its own timeline, one I couldn't schedule or accelerate. Between those two timelines sat the session, which was now a point where they could intersect.

I opened the orientation materials and started from the index.