The richest man started taking advantage of loopholes after joining Alibaba.

Even after Fang Yuan left, the white light still shone through the crack in the door.

Lin Che stared at the light for a few seconds, then stood up and closed the door.

With a click, the corridor lights went out, leaving only the gray-white sunlight coming in from the window and the white light from the overhead fluorescent lights in the office.

He returned to the table and sat down.

The little brown coffee dot on the table is still stuck in the wood grain, the kind that can't be rubbed off.

Fang Yuan has already taken the Nestlé 3-in-1, but a faint ring of marks remains on the corner of the table.

He didn't touch the computer immediately.

First, unplug Shen Nan's USB drive from the computer and put it in the drawer.

The table showing the five circuit breaker options was still open on the screen. He closed it, and a pop-up prompt asked if he wanted to save the changes. He clicked no.

The screen is clean.

Then he opened the Abyss backend.

The login screen is very simple: a black background, an input box in the middle, no logo, no name, nothing at all.

After entering the password, it took a second for the system to load in the background.

The left side is the navigation bar.

He didn't click on the data panel, the forecasting module, or anything related to the business.

He selected the bottom option, which was in small gray text.

System logs.

When the log page opens, it is initially blank, and then the records are loaded line by line from top to bottom.

Arranged in reverse chronological order, with the newest at the top.

Each line is an operation record, containing a timestamp, operation type, module name, and operator ID.

He didn't watch the latest version.

I simply entered a date into the search box.

2020-01-03.

The search results have been refreshed, and only three records remain.

First entry: 2020-01-03, 01:44:12, Parameter reading, module prediction_core, operator ID: system_auto.

Second: 2020-01-03, 02:17:43, parameter modification, module prediction_core, there is only one placeholder in the operator ID column.

Item 3: 2020-01-03, 02:17:44, Parameter validation, module prediction_core, operator ID: system_auto.

Three records.

The first and third items are both automated operations by the system and have complete operator ID labels.

The middle one, 02:17:43, has an empty operator ID field; there's nothing there.

He moved the mouse over the second record and clicked on the details.

A sub-panel expanded from the details page.

Changes: The weight values ​​of the three parameters in the prediction_core module have been adjusted.

Parameter 1: risk_tolerance_baseline, adjusted from 0.34 to 0.41.

Parameter 2: confidence_threshold_min, adjusted from 0.72 to 0.65.

Parameter 3: user_behavior_weight, adjusted from 0.00 to 0.18.

Three parameters, three numbers changing.

The first parameter increases Abyss's risk tolerance, the second parameter lowers the minimum confidence threshold, and the third parameter changes the user behavior weight from zero to 0.18.

The third parameter.

user_behavior_weight.

From zero to 0.18.

The reserved field that Fang Yuan asked about today is called user_behavior_pattern.

The modified parameter is called user_behavior_weight.

One is the column, and the other is the weight.

The names are different, but they refer to the same thing.

At 2:17:43 AM on January 3, 2020, Abyss added a feature to itself.

The purpose of this function is to observe user behavior patterns and incorporate the observed results into the prediction calculations.

It wasn't written by Lin Che.

It wasn't written by anyone.

The operator ID field has only one short horizontal line.

He stared at the three records on the screen for a long time.

The white light from the fluorescent lamp caused a slight reflection on the screen. He adjusted the screen angle, and the reflection disappeared, making the three records clearer.

01:44:12, Read.

02:17:43, Modified.

02:17:44, Verification.

Thirty-three minutes and thirty-one seconds elapsed between reading and modifying the data.

There was a one-second interval between modification and verification.

Thirty-three minutes.

Abyss took 33 minutes to read its own parameters, and then completed the modification and self-verification in less than a second.

Thirty-three minutes of reading, one second of action.

What was Abyss doing during those 33 minutes?

Reading a set of parameters doesn't take thirty-three minutes; a few milliseconds are enough.

The 33 minutes shown in the log is a blank period of time after the system finishes reading and before the modification occurs.

There were no operation records, no module calls, nothing happened.

But after thirty-three minutes, the three parameters changed.

If Fang Yuan's judgment is correct.

What if what's retained in 20% isn't the algorithm, but willpower?

Those thirty-three minutes are the process by which it makes its decision.

He did nothing.

There were no modifications, no rollbacks, no log deletions, and no annotations or notes left anywhere.

He just watched.

The mouse hovers over the details page of the second record, and the arrow remains stationary.

The air conditioner was blowing warm air from the left vent. The time in the lower right corner of the screen jumped to 3:47 PM.

He's been sitting there for almost an hour.

I closed the details page.

I turned off the log.

I closed the Abyss backend.

Sign out.

The screen returned to the desktop.

Four icons.

Lv4, Abyss-v4, if, screenshot_20221226.

Just like yesterday, nothing more, nothing less.

He glanced at the icon of the Abyss-v4 folder.

empty.

But Abyss itself is not empty.

It spent 33 minutes adding a feature to itself at 2 a.m. one day, and has been running ever since.

He picked up his phone and opened WeChat.

I turned to Fang Yuan's chat window.

I typed a line of text.

Do you still have that 13-page printed copy?

send.

I waited for about five seconds.

The message has been read, and the time next to it has jumped.

A message appeared at the bottom of the dialog box: "The other party is typing."

Two seconds later, the message popped up.

"exist"

One word.

Fang Yuan never types much.

Lin Che put down his phone.

Before the screen went dark, he saw the green online icon next to Fang Yuan's profile picture.

Fang Yuan was also awake.

They were thinking about the same thing.