"Okay... Let's get to work," Tyler said, plopping into his bed and causing it to squeak desperately under his weight.
He took the laptop out from the box and pressed the power button, powering it on.
He allowed the laptop to boot. And while it did that, he turned his attention to the phones and started setting them up.
A few minutes later, the laptop was done booting and Tyler started setting it up. He made sure to install the softwares and programmes he would need for his project.
It took him time but he was finally done with it. With the installations done, it was now time to get to work.
Immediately, Tyler went into deep focus, as he started designing the structure of his model, mapping out the logic behind it, establishing the framework it would follow, and most importantly—defining the new core mechanics it would run on.
Writing the codes weren't the first thing to but that. He has to go through the information in his head and look for a way to extremely dumb the down the highly advanced knowledge in his head, so that he doesn't write a code that would make his $2,000+ fossil laptop go up in smokes.
To say it was easy would be a lie. It was quite difficult and Tyler felt like he was suffering from success.
Though it took him some time, he was finally able to get it done and his strategy was ready.
The next thing was to start writing the codes and that was what he did.
His strategy was built around a model and indicator granted through the system: Volatility-Enhanced Learning & Uncertainty Exchange Model (VELUX).
Yes, big name.
And yes—it works just as big as they sounded.
Tyler gave a small at the memory of trying to summarize it in his head earlier. Trying to explain it in full would take hours, maybe days. But he had boiled it down to its essential essence.
VELUX functioned like a supernatural early warning system for smart-money moves—tracking hidden liquidity shifts before they manifested in visible market action.
It analyzed data far beyond price and volume, processing order book behavior, transaction flow depth, and even psychological pattern disruption.
It also function as an indicator, as it could detect micro-volatility pulses buried deep in the data stream. It wasn't fooled by sideways price action or manipulation.
It sensed real tension beneath the surface, measuring when liquidity was about to "snap," like a stretched rubber band recoiling.
And perhaps the most frightening part? It can evolve.
As in—adapted over time. It doesn't rely on static rules or fixed conditions. The more data it consumes, the sharper it becomes. Like an intelligent predator learning the patterns of their prey.
And yes, this is the extremely dumbed version down version of the original thing.
Tyler's hands flew across his keyboard, followed by the consistent clacking sound of his keyboard.
For someone who hasn't done anything related to coding in his previous life, he felt that this would be difficult.
But surprisingly when his fingers touched the keyboard, he saw that it was actually easier than be expected.
This wasn't to say that it wasn't in any way difficult but it was easier than he thought it would be.
Initially he had felt that he needed to learn and familiarise himself with a programming language.
But he didn't as there was this vague feeling he had immediately after he woke up from the absorption process. And it was that feeling that he followed.
As Tyler continued writing the codes, he noticed that more and more information were starting to flow into his brain.
After writing more than 300 lines of codes, Tyler wasn't anywhere close to being done.
At this point, he realised that he wasn't using any programming languages known to anyone on Earth.
According to what he gathered from the information in his head, the programming language he's using was something from the system, as it came embedded in one of the Specialised Knowledges.
One would expect something like this not to surprise him anymore but he was still left speechless by it.
The reason for this was because of the programming language's features.
It wasn't just some fancy script. It was an encrypted, self-defensive coding system capable of:
Self-obfuscation: Anyone else looking at it would see nothing but gibberish nonsense.
It might sound similar to encryption but more advanced.
Cross-language binding: It could interact with Python, C++, Java, Solidity, and even low-level assembly effortlessly.
Execution cloaking: The code could run silently in background environments without triggering OS alerts or firewalls.
Autonomous defense: If any intrusion attempt was detected, it would rewrite core pathways instantly.
In simpler terms? It was unhackable and untraceable.
Without needing to be told, Tyler understood how extremely valuable what he has in his possession is.
With just $10,000, he now has what mega corporate entities and world powers would give fortunes, and even kill for.
But Tyler wasn't worried as he never had the slightest intention to reveal to anyone anything the system of his regression. Not even his family.
Time flew and it was already evening, and Tyler was finally done with the code.
Looking at the more than one thousand lines of codes, he sighed and smiled.
With the codes ready, the next thing was to run it. But he didn't do that yet, as he started going through it again to make sure that he didn't make any mistake.
He would soon be called for dinner but he would love to finish this first and have it running in the background, before going downstairs.
"Perfect and ready to go," he said, after he was done crosschecking.
His system architecture now consisted of multiple polished modules:
Data fetching via real-time APIs, optimized to pull clean, unlagged streams from multiple Tier 1 sources.
Trade logic, meticulously designed using VELUX. Then, position sizing and account checks, built with what could be called the system's advanced version of Bayesian logic, dynamic leverage thresholds, and multiple kill-switch conditions to avoid catastrophic loss scenarios.
SMTP email and SMS integration for receiving alerts and decision logs. Every action the bot would take would be fed directly to him.
The SMTP email alerts as the main alert system and the SMS would be a backup for critical events like market crashes or any potential bot errors.
The UI overlay looks good with a clean, dark-themed dashboard. It displayed not just open positions, but trade rationale, VELUX readings and tension arcs, and a confidence index.
With everything ready, it was time to run the code. Taking a deep breath and letting it out slowly, he clicked on the enter button.
The next moment, the final screen rendered: a full-screen schematic of the finished architecture.
Main Frame: VaultX
Lines of color-coded flow connected modules like synapses. Blue for market data. Red for logic routes. Yellow for liquidity responses. Purple for adaptive triggers. Green for post-trade analytics.
But Tyler wasn't done yet, as he switched to the backtesting terminal.
A new set of interfaces loaded. Multiple options appeared for ticker selection, timeframe resolution, and data range.
He clicked open a menu and began selecting tickers: SPY, QQQ, TQQQ, SQQQ, IWM, VTI.
He also added individual stocks.
The following moment, a multi-threaded simulation field lit up.
Each ticker would run independently, using historical minute-level data from the past ten years, with random event stressors enabled.
What Tyler was looking for wasn't just profitability. He was also watching for something deeper:
Overfitting: Would the model fail outside clean conditions?
Drawdown resilience: How bad did it bleed during false signals?
Sharp Ratio, Alpha, Beta, Win Rate, Max Consecutive Losses.
He toggled every metric accurately and clicked {Start Simulation}.
The screen flared into motion. Green and red bars danced around the screens, as the module started churning through millions of data points per minute.
The bot strategy was now running in parallel, acting as if it was live, as it read through historical markets in real time, adapting to volatility, tracking liquidity.
It was like a shark sniffing blood in dark water.
And as each second passed…
The dashboard began to populate with numbers.
Backtest Results Summary (Capital: $100,000 per Ticker)
1. SPY Strategy
Win Rate: 68.2%
Avg Profit per Trade: $142
Max Drawdown: 3.4%
Sharpe Ratio: 2.17
Net ROI (3 years): +341%
Net Profit: $341,000
...
QQQ Strategy
Win Rate: 71.5%
Avg Profit per Trade: $165
Max Drawdown: 4.1%
Sharpe Ratio: 2.41
Net ROI (3 years): +397%
Net Profit: $397,000
...
TQQQ Strategy
Win Rate: 59.8%
Avg Profit per Trade: $275
Max Drawdown: 14.7%
Sharpe Ratio: 1.89
Net ROI (3 years): +762%
Net Profit: $762,000
.....
.....
.....
The list was nearly endless but for a former financial analyst like Tyler, going through them and understanding what they meant was very easy.
"Good," Tyler nodded to himself in satisfaction, at the data in front of him.
Each line glowed green. Not a single one had failed. But more importantly, none had spiked unusually high, which meant the models weren't curve-fitting.
The backtest showed that, despite not being optimized for specific historical events, VaultX proved its dynamic capability through self-learning and adaptive behavior.
Tyler still wasn't done, as he continued by initiating market crash simulation testing, using the recent 2008 event and even synthetic black swan events.
He activated cross-ticker model switching, seeing how one bot performed when fed inputs from unrelated tickers. And he even corrupted data feeds mid-run.
But VaultX didn't disappoint, as it adapted, learned and became even better.
"Perfect," he smiled in satisfaction.
With the trading bot, VaultX, completed, all that's needed for Tyler now was to either start with live trading directly or do a paper trade first.
And he decided to do paper trading first. But he won't be able to do that yet, as he need a trading account to do that. Not only that, he will also need a bank account.
But as an underage, Tyler can't create a brokerage or bank account on his own.
"I guess you have more roles to play in this life, David," Tyler smiled to himself, leaving his room and making his way downstairs for dinner.