Monday. October 21st. 7:00 AM — Research Lab.
Dr. Yuen slid a single printed page across the desk without looking up from her own screen.
Aren picked it up. It was a formal letter — Sovereign University Department of Research Collaboration, signed by a Professor Aldric Mosen, Deputy Chair of Quantitative Methods. The subject line: Proposed Data Partnership — Lattice Investment Group & Yuen Research Group.
He read it twice. The language was institutional, measured, and on its surface entirely reasonable: the Lattice was offering access to their proprietary real-time market dataset — fifteen years of granular transaction data not available through any public channel — in exchange for co-authorship rights on any publication that utilized the data. Standard collaborative arrangement. The kind that appeared in academic journals as gratitude footnotes all the time.
The subtext was the kind you only read if you understood what the Lattice was.
Co-authorship rights meant co-ownership of the methodology once applied to their data. Standard collaborative arrangement meant the Lattice's legal team had a clause somewhere that allowed them to restrict publication of findings they found inconvenient. Proprietary real-time data meant the tool they were offering was also a leash — once the research was built on it, the research couldn't function without continued Lattice access.
"Mosen," Aren said. "Word Knowledge had him connected to a Lattice advisory board."
"He joined it eight months ago," Dr. Yuen said. "Three months after I declined Victor Solwyn's first direct approach."
Aren set the letter down. "They put an institutional intermediary between themselves and the ask to make the refusal harder."
"Refusing Mosen means refusing the Department," she confirmed. "Which creates a governance issue I'd have to manage carefully."
"Unless the refusal comes from a research governance principle rather than personal objection," Aren said. "If you decline on the basis of your lab's data independence protocol — a protocol that predates Mosen's involvement and applies to all partnerships equally — there's nothing personal to escalate."
She looked at him. "My lab doesn't currently have a formal data independence protocol."
"It will by Thursday," he said. "I'll draft it."
A pause — the pause of a woman who was recalibrating how much of what she had thought was her own forward planning had been anticipated by a nineteen-year-old who had been in her lab for six weeks. "Three conditions," she said. "It must apply genuinely to all partnership offers — no carve-outs. It must pass the Faculty Research Standards committee. And it must be filed before Mosen expects a response."
"Thursday," Aren repeated.
She nodded once and returned to her screen.
Tuesday. October 22nd — Opportunity Dominance Assessment.
He ran the prerequisite check during his evening study session with AION's overlay active, tracking the four mastery thresholds the system had flagged as required for Opportunity Dominance to unlock.
[OPPORTUNITY DOMINANCE — PREREQUISITE TRACKER]
[REQUIREMENT 1: Technical/Algorithmic Mastery ≥ Lv3]
[CURRENT: Algorithmic Programming Lv2 | Progress: 67% toward Lv3]
[REQUIREMENT 2: Business & Operations Mastery ≥ Lv3]
[CURRENT: Business/Economy Lv2 | Leadership Lv1 | Progress: 71% toward Lv3]
[REQUIREMENT 3: Financial Mastery ≥ Lv3]
[CURRENT: Finance/Markets Lv2 | Network Analysis Lv1 | Progress: 74% toward Lv3]
[REQUIREMENT 4: Academic Research Mastery ≥ Lv2]
[CURRENT: Academic Research Lv1 | Progress: 44% toward Lv2]
[ESTIMATED UNLOCK: 8–12 weeks at current pace | Accelerated by Superbrain use]
Eight to twelve weeks. He was two months into first semester. At the current trajectory, Opportunity Dominance would unlock midway through second semester — if he maintained the pace and kept pushing the mastery domains that fed into it. Technical mastery was the constraint. He needed to advance Algorithmic Programming from Level 2 to Level 3, which required practical application beyond the coursework he was currently completing.
He noted the gap and identified the solution simultaneously: Dr. Yuen's research methodology revision required building an automated data-cleaning pipeline for the new sampling framework. He had been handling it manually. If he rebuilt it programmatically — properly, in a way that could scale — the technical mastery domain would advance through genuine application rather than coursework alone.
He added it to the Tuesday morning research session agenda and moved on.
Thursday. October 24th — Data Independence Protocol filed.
The document was four pages. Aren had written the first draft in two hours on Tuesday evening — Superbrain active for the legal language sections, where precision mattered more than speed — and Dr. Yuen had made seven substantive edits on Wednesday that sharpened it without changing its essential structure.
The Yuen Research Group Data Independence Protocol established three principles: that all data used in published research must remain accessible to the research team independent of the providing partner; that no partner received co-authorship rights on methodology without independent replication of findings; and that any data partnership offer must be reviewed against these principles before response, without exception.
Dr. Yuen submitted it to the Faculty Research Standards committee at 9 AM Thursday.
At 11 AM, Aren received a message from the Department coordination office: Professor Mosen would like to schedule a follow-up discussion on the proposed Lattice partnership at his earliest convenience.
He forwarded it to Dr. Yuen with one line: The protocol applies.
She replied with two words: Already sent.
Friday. October 25th — The Single-Trade Signal.
AION flagged it at 4:17 PM while Aren was midway through the automated pipeline rebuild.
[AION: Stock Foresight — Single-Trade Protocol Alert]
[ELEVATED SIGNAL DETECTED — Available for Single-Trade Deployment]
[SIGNAL: KAELMOOR HEAVY INDUSTRIES | +26.4% | 96 HOURS]
[CONFIDENCE: MAXIMUM — Single-Trade eligible threshold confirmed]
[DEPLOY UP TO: 250,000 Veltrions]
[WINDOW: Signal valid for 12 hours — deploy before 04:17 AM Saturday]
He stopped typing.
+26.4% on 250,000 Veltrions. Gross return: 66,000 Veltrions. Net after brokerage: approximately 65,250V.
In ninety-six hours.
He had 556,780 Veltrions in the bank. The deployment would leave him 306,780 liquid — comfortable, with the monthly income streams covering all expenses several times over. There was no legitimate argument against it.
"Aion. Execute single-trade — Kaelmoor Heavy Industries. Full 250,000V allocation."
[AION: Single-Trade Protocol executing.]
[POSITION: KAELMOOR HEAVY INDUSTRIES — 250,000V deployed]
[BANK: 556,780 → 306,780 VELTRIONS]
[SETTLEMENT: Projected Tuesday morning — auto-liquidate at target]
[SINGLE-TRADE UNLOCK: CONSUMED — next available after 10/10 milestone cycle]
He returned to the pipeline rebuild. The code was more interesting than watching a trade position sit in the market, and he needed the Algorithmic Programming mastery advancement more urgently than he needed to observe a certainty in progress.
[PHYSICAL ADAPTATION — WEEK 8-9]
[STR: 46 | AGI: 46 | STA: 46 | INT: 179]
[CL: 358/358 — Stage 2 × INT 179]
[ALGORITHMIC PROGRAMMING: Lv2 → Lv3 threshold progress: +38% (pipeline rebuild contributing)]
— End of Chapter 33 —