Skip to main content
  • Home
  • Library
  • Read
    • Popular
    • Charts
    • Browse
    • Categories
    • Wikis
    • Glossary
  • Request
  • Activity
  • Leaderboard
  • Help
Our Apps
  • DaoSearch
  • Narratorr
Social
  • Discord
  • Patreon

Recaps

The AI Wave Tycoon's Rise
VolumesArcsSummaries

Arc 9Riding the Wind Takes Flight

Source Code Technology launched Riding the Wind, weathered criticism, and faced Neus’s competing Atlas as the tool gained users and enterprise interest. Meanwhile, Han Luyi advanced Glutinous Rice Ball’s training amid interference, and Sight leveled up as training neared completion.

  • Han Luyi and Jiang Songran reviewed applicants and procurement plans for domestic AI infrastructure as Zheng Xiaobo considered bringing Han back to Dingsheng.
  • Jiang Yixin tested the coding agent, named it Riding the Wind with Su Niannian, and launched its beta, which drew users but also sharp criticism after CodeMonkey Old Zhang reported a damaging code change.
  • Ryan tested Riding the Wind on difficult coding tasks, then ordered Neus to analyze it and accelerate Atlas, while Han Luyi argued for safeguards and Su Niannian prepared a public launch.
  • Jiang Yixin demonstrated Riding the Wind at Source Code Technology’s annual party and opened its public beta, while employees celebrated and Han Luyi took Zhang Biao to Lu'an for the New Year.
  • Han Luyi corrected anomalous training data, stabilized Glutinous Rice Ball’s pretraining, and began annealing as Zhang Chi pushed Dingsheng to build an enterprise-focused competitor.
  • Jiang Yixin recognized that NeusAtlas copied Riding the Wind’s closed-beta features, and Han Luyi agreed to focus on the domestic market and let her decouple the product from specific models.
  • Han Luyi used Sight to identify and reverse computing interference against Glutinous Rice Ball, while developers debated Neus’s claim that Atlas was first and Riding the Wind registrations neared two million.
  • Jiang Yixin drafted enterprise pricing as clients asked for a paid version, Han Luyi monitored the final training and data-center deployment, and Sight leveled up.
Chapters 202–226 Vol. 3 Read

Ch. 202This Was a Policy-Driven Procurement

Jiang Songran found strong interest from AIInfra workers eager to develop domestic GPU alternatives, while Zhang Biao carefully prepared to inspect a purchase of graphics cards. At Dingsheng, Zheng Xiaobo learned of Source Intelligence Technology’s plans and dismissed them as policy-driven procurement, while considering bringing Han Luyi back to the company.

  • Han Luyi told Jiang Songran not to spend his connections recruiting, but Jiang said more than a dozen resumes had already arrived from people who wanted to work with him on domestic AI infrastructure.
  • Han Luyi asked Jiang Songran to forward the resumes so they could review them together.
  • Zhang Biao reviewed Jiang Songran’s procurement instructions and identified equipment testing, liability, and replacement timelines as key points to verify in Pengcheng.
  • Lin Shaowen told Zheng Xiaobo that Jiang Songran had joined Source Intelligence Technology and that the company planned to recruit AIInfra staff and buy domestic graphics cards.
  • Zheng Xiaobo learned that Source Intelligence Technology had received financing from He Yunshen and an electric-power-backed investment firm, and concluded its planned purchases were policy-driven.
  • Zheng Xiaobo judged Han Luyi to have foresight and connections, and considered acquiring his company and bringing him back to Dingsheng.
Read chapter

Ch. 203The Three Missing People

Jiang Yixin reviewed the coding Agent’s strong internal beta results and asked Su Niannian to approve its first external beta. Su Niannian questioned why three of the thirty developers had not used it, leaving Jiang Yixin’s request unresolved.

  • Jiang Yixin reviewed internal data showing the coding Agent boosted assisted code merges, especially for simple tasks, but struggled with complex work.
  • Li Ting and Qian Xiaole reassured Jiang Yixin that the Agent was useful and that developers would like it.
  • Jiang Yixin presented the data and report to Su Niannian and requested that the first beta begin the next day.
  • Su Niannian asked whether Jiang Yixin had spoken with the three developers who had not used the Agent.
Read chapter

Ch. 204Time for the Exciting Naming Part Again

Jiang Yixin reviewed the three developers who had not adopted the programming agent with Su Niannian, then prepared a closed beta plan and renamed the product Riding the Wind. The chapter ended with Jiang Yixin updating the landing page ahead of the planned launch the next morning.

  • Su Niannian asked Jiang Yixin why Chen Jianye, Liang Wei, and a BugKiller engineer had not used the programming agent, revealing that some lacked suitable tasks while another disliked the workflow.
  • Jiang Yixin added the adoption issues to her report and explained that developers who did not want to use the agent might resist learning new methods.
  • Jiang Yixin presented her plan to recruit BugKiller users for the closed beta, and Su Niannian advised her to set realistic expectations about the tool’s capabilities.
  • Su Niannian and Jiang Yixin chose the product name Riding the Wind, and Su Niannian approved a budget for a logo before the open beta.
  • Jiang Yixin returned to her workstation and updated the landing page with the new name, which Qian Xiaole praised.
Read chapter

Ch. 205I Advise You Not to Release It

Jiang Yixin and her team launched Riding the Wind’s beta, which attracted users and encouraging early usage data. The launch was then shaken by a prominent tech influencer’s warning about dangerous AI-generated changes and a wave of anger on Source Code Technology’s announcement.

  • Jiang Yixin finalized the Riding the Wind landing page and kept a warning against using it for high-complexity cross-module refactoring.
  • Jiang Yixin and Qian Xiaole watched the beta launch as all fifty public invitation codes were claimed, activations reached sixty-seven, and the first users reported an initial pass rate of about 80%.
  • Jiang Yixin saw all one hundred invitations activated and hundreds of calls made within three hours, while Qian Xiaole stayed behind to monitor the beta.
  • Qian Xiaole showed Jiang Yixin a popular post by CodeMonkey Old Zhang, who described Riding the Wind deleting necessary payment deduplication logic and urged programmers not to use it or Source Code Technology to release it.
  • Little Yang alerted Li Ting that the company’s beta announcement was being flooded with comments, including a top comment accusing Source Code Technology of threatening programmers’ livelihoods.
Read chapter

Ch. 206Ride the Wind

Jiang Yixin reconsidered the risks Old Zhang had raised about Riding the Wind, then resolved to keep developing it and make it an industry leader. Han Luyi called Old Zhang to discuss the criticism, while NeusAI CEO Ryan learned about Riding the Wind and began looking into it.

  • Li Ting disabled comments, posted a restrained announcement, and adjusted the display of feedback after Old Zhang’s negative review spread.
  • Jiang Yixin realized that AI agents’ inconsistent outputs could undermine the determinism programmers relied on.
  • Han Luyi asked Jiang Yixin whether Old Zhang was right, and she decided to continue developing Riding the Wind and set industry standards.
  • Han Luyi called Old Zhang, agreed with his criticisms, and asked whether others would build such a product if Source Code Technology did not.
  • Ryan received Sarah’s message about Riding the Wind, opened its beta launch page, and translated it into English.
Read chapter

Ch. 207How did they do it?

Ryan tested Riding the Wind against Neus Atlas and discovered it could understand an unfamiliar codebase, refactor difficult logic, and pass challenging tests. He called Neus’s leaders to an emergency meeting, then realized Riding the Wind used Neus’s own Mercury Model and wondered how Source Code Technology had built such an effective tool.

  • Ryan dismissed Riding the Wind as a publicity stunt, then tested it by asking it to add cascading cancellation to his Go project.
  • Riding the Wind identified the relevant event bus, refactored the tangled legacy logic, wrote unit tests, and passed them on its first try.
  • Ryan tested Riding the Wind on Atlas’s notoriously difficult case-42, and it passed within five minutes.
  • Ryan called Sarah and ordered her to assemble Neus’s department heads for an online meeting at eleven, then contacted CTO John Snow.
  • Ryan read the forum post Sarah had sent and concluded that Old Zhang had blamed Riding the Wind for the Mercury Model’s aggressive decision to remove deduplication logic.
  • Ryan recognized that the Mercury Model powered Riding the Wind and wondered how Source Code Technology had built its workflow orchestration tool.
Read chapter

Ch. 208Fortunately, they had no large model of their own

After Ryan demonstrated that Riding the Wind consistently outperformed Atlas, he ordered Neus to accelerate Atlas’s launch and study the rival product. He reassured the team that Riding the Wind relied on Neus’s Mercury Model, but the chapter ended with Atlas still far from ready and the market moving too quickly to wait.

  • Ryan showed John and Neus’s employees a live demonstration of Riding the Wind completing a coding task in about three minutes.
  • John called Riding the Wind more polished than Atlas, while Evan asked to see the demonstration again and Ryan stressed that it had worked three times.
  • Ryan learned that Riding the Wind had only a hundred Chinese beta users and no overseas attention, then ordered John to launch Atlas in four weeks.
  • Ryan tasked Evan’s team with analyzing Riding the Wind and reporting within forty-eight hours on how to reproduce it.
  • Ryan told the team that Riding the Wind relied on Neus’s Mercury Model and ordered Michael to promote Atlas widely without mentioning the Chinese company.
  • After the meeting, John warned Ryan that Atlas was nowhere near ready, and Ryan replied that neither was the market.
Read chapter

Ch. 209Let the bullets fly a little longer

Han Luyi persuaded CodeMonkey Old Zhang that Riding the Wind’s risks should be managed rather than ignored, and promised improvements for the next version. Old Zhang updated his forum post, but criticism continued as Han Luyi turned to the product team; meanwhile, Dingsheng Cloud’s Zhang Chi dismissed the beta as unimportant.

  • Han Luyi argued that AI coding tools were inevitable and proposed clearer change approvals and checkpoints so users could review or roll back Riding the Wind’s modifications.
  • Old Zhang acknowledged Han Luyi’s point, then updated his forum post to say the issues affected the whole field and that he hoped Source Code Technology would find a better answer.
  • Jiang Yixin warned that Old Zhang’s revised post had not stopped public criticism, and Han Luyi told the team to focus on improving the product before taking her to see Su Niannian.
  • At Dingsheng Cloud, Zhang Chi heard that Source Code Technology had begun testing Riding the Wind but declined to examine it, deciding the company posed little threat.
Read chapter

Ch. 210Even bad publicity is publicity

After online controversy over Riding the Wind drove a surge in beta interest, Su Niannian and Han Luyi decided to turn Source Code Technology’s annual party into a public product launch. Jiang Yixin agreed to host the launch, which was set for the following Thursday.

  • Han Luyi told Su Niannian and Jiang Yixin that Old Zhang had updated his post, but the online debate was already difficult to control.
  • Su Niannian showed Jiang Yixin that beta users were active, had completed hundreds of tasks, accepted most changes, and helped grow the waiting list to more than 13,000.
  • Su Niannian and Han Luyi decided to use the controversy to introduce Riding the Wind to the public and open a limited-use public beta at the company’s annual party.
  • Su Niannian proposed inviting media and livestreaming the launch so the company could demonstrate the product and explain its vision.
  • Han Luyi asked Jiang Yixin to host the launch, and she agreed to do it well.
Read chapter

Ch. 211A battle of wits in the president's office

Han Luyi expanded Source Code Technology’s hiring plans while the company prepared its launch event, and Zhao Wenyuan and Jiang Songran interviewed a candidate whose polished answers made them suspect he was management material. The chapter ended as Han Luyi arrived and greeted Liu Huo, who had introduced himself by a different name during the interview.

  • Han Luyi asked Shen Congyun to find secretaries for Su Niannian and himself and to accelerate recruitment for AIInfra before the Spring Festival.
  • Jiang Songran and Zhao Wenyuan discussed an unimpressive candidate, then began interviewing the late-arriving Liu Huo, whose résumé belonged to Liu Yu.
  • Liu Huo gave detailed answers about distributed systems, incident response, and monopolies, impressing both interviewers.
  • Zhao Wenyuan asked Liu Huo which languages he preferred, and Liu Huo said he primarily used Chinese and could also work in English and Japanese.
  • Han Luyi arrived late to the interview and greeted Liu Huo by name.
Read chapter

Ch. 212I am the initiator of Riding the Wind

At Source Code Technology’s first annual party, Jiang Yixin launched Riding the Wind with a live demonstration of the AI agent adding tree-based version management to its own codebase. After it diagnosed and fixed a failing test, Jiang announced the public beta and closed by introducing herself as the product’s initiator.

  • Jiang Yixin prepared to present Riding the Wind at Source Code Technology’s vintage-themed annual party, while Li Ting coordinated the livestream and the team gathered to watch.
  • Jiang Yixin opened the launch with a story about an overworked engineer and explained that Riding the Wind was designed to work alongside programmers as an engineering colleague.
  • Jiang Yixin asked Riding the Wind to add branch management to its own codebase, and the agent analyzed the project, modified files, and generated a task progress view.
  • Riding the Wind’s first test run failed because branch switching did not persist the current branch, so the agent identified the cause, fixed the code, and passed the rerun.
  • Jiang Yixin demonstrated the completed branch-management features and announced Riding the Wind’s public beta and enterprise trial applications.
  • After Li Ting prompted her to introduce herself, Jiang Yixin told the audience she was Source Code Technology’s head of product and the initiator of Riding the Wind.
Read chapter

Ch. 213Annual Meeting Must Go On

After Jiang Yixin’s successful Riding the Wind launch, Source Code Technology held its first annual meeting, where the raffle showcased the agent’s coding abilities and Han Luyi announced generous year-end bonuses. The celebration ended with employees cheering over a bonus equal to six months’ salary.

  • Li Ting ended the launch event and invited media guests to stay for Source Code Technology’s annual meeting.
  • Employees took Polaroid photos, and Li Ting praised Jiang Yixin as the face of Source Code Technology.
  • Zhang Biao won the first two raffle prizes, and Han Luyi explained that the program allowed repeat winners because each draw was independent.
  • Qian Xiaole used Riding the Wind to update the raffle code so past winners would be removed from later draws, and the programmers reviewed its changes.
  • Han Luyi announced that every current employee would receive a year-end bonus of six months’ salary, prompting the employees to cheer.
Read chapter

Ch. 214Boundless Oceans Vast Skies

At Source Code Technology’s annual meeting, former Dingsheng employees performed a comic skit mocking their old company’s bureaucracy, while Han Luyi reminded himself not to let his new company repeat Dingsheng’s mistakes. Su Niannian closed the event with a song that brought the employees together in a hopeful chorus.

  • Chen Jianye, Li Wen, and Zhang Xingyan performed a skit satirizing Dingsheng’s meetings, processes, and innovation approvals.
  • Han Luyi laughed at the skit, recognized the experiences behind its jokes, and reminded himself not to let Source Code Technology become like Dingsheng.
  • Su Niannian surprised the employees by taking the stage in an evening gown to sing a song she had performed in university.
  • Jiang Songran began singing along, moved by memories of his youth, and Zhao Wenyuan noticed tears in his eyes.
  • The employees gradually joined Su Niannian and Jiang Songran, and the entire hall sang together.
Read chapter

Ch. 215Mr. Zhang, You're Working Far Too Hard

Han Luyi invited Zhang Biao to drive with him to Lu'an and spend the New Year with his family after learning Zhang Biao would otherwise be alone. Meanwhile, Zhang Chi ordered Dingsheng Cloud to build a competing product on an accelerated schedule and delayed his own return from Sanya to oversee it.

  • Han Luyi confirmed that Zhao Wenyuan would monitor Glutinous Rice Ball's pretraining during the holiday, while Jiang Songran reported that the data center cluster was ready for further testing.
  • Han Luyi learned Zhang Biao would spend the holiday alone in Haicheng, invited him to drive to Lu'an, and told Zhou Min to prepare an extra place at home.
  • Han Luyi and Zhang Biao packed and set off for Lu'an after Su Niannian learned they would be traveling together.
  • Zhang Chi reprimanded his competitor-analysis director for failing to report Riding the Wind's public beta and demanded a report by the next day.
  • Zhang Chi ordered Liu Bo to produce a usable product competing with Riding the Wind within two weeks, then rescheduled his return from Sanya so he could supervise the project.
Read chapter

Ch. 216Done Is All That Matters, It Won't Be Released

Han Luyi brought his colleague Zhang Biao home to celebrate the New Year with Zhou Min, who welcomed him and put him to work preparing the feast. Meanwhile, Dingsheng rushed its developers into a holiday project, and two engineers hinted that the finished work would never be released.

  • Han Luyi and Zhang Biao arrived at Gaoyuan Residential Community, where Zhou Min greeted them and invited Zhang Biao to stay for the New Year.
  • Zhou Min prepared a large New Year's feast, and Zhang Biao impressed her with his cooking skills while Han Luyi struggled to help.
  • Han Luyi exchanged New Year messages with Su Niannian and Gu Siyue, who said she was spending the holiday in Kunming.
  • At Dingsheng, Director Wang and Liu Bo ordered teams to build a competing product on a tight schedule through the holiday.
  • Two software engineers privately said the project only had to be completed and would not be released.
Read chapter

Ch. 217Learning Computer Science Isn't Enough—You Need to Study AI

Han Luyi spent New Year’s with his mother and relatives, where his cousin Li Wei showed how he had used an AI platform to build an app for his restaurant. As Zhou Muzhi considered studying computer science and Han Luyi reflected on AI’s growing reach, an alert reported that a Dingsheng Cloud pre-training run had failed.

  • Zhang Biao made dumplings for Han Luyi and Zhou Min, then asked Han Luyi to keep his layoff and company a secret from his mother.
  • Han Luyi and Zhou Min visited his maternal grandparents for New Year’s, where Han Luyi reunited with Li Wei and saw Zhou Muzhi.
  • Han Luyi’s eldest uncle praised Li Wei’s restaurant app and advised Zhou Muzhi to study AI instead of computer science.
  • Li Wei explained that he had built the app with Open Things, prompting Zhou Muzhi to download the platform and ask Han Luyi about studying computer science.
  • Han Luyi received an alert that a Dingsheng Cloud pre-training run had failed.
Read chapter

Ch. 218If You Want to Ask, Go Ahead. I'm Not Asking Anyway

Han Luyi used Sight to find and fix corrupted training data while Zhao Wenyuan restarted the model. Elsewhere, Liu Bo and Director Wang avoided reporting their project’s weak results to Zhang Chi, and Gu Siyue reconsidered messaging Han Luyi after her mother raised moving back to Beijing and a blind date.

  • Han Luyi reviewed Zhao Wenyuan’s anomalous training samples, used Sight to identify pseudo-structured fragments, and added rules to remove them.
  • Zhao Wenyuan processed the data with Han Luyi’s revised rules and restarted training.
  • Liu Bo and Director Wang discussed Qianyuan’s weak model results and agreed to wait until the next afternoon before contacting Zhang Chi.
  • Gu Siyue rejected her mother’s suggestion to meet a prospective date in Beijing and complained that her father was working through the New Year.
  • After hugging her mother, Gu Siyue opened her chat with Han Luyi, typed a message, then deleted it without sending.
Read chapter

Ch. 219Tell Me, How's the Progress?

Han Luyi learned that his mother knew about his layoff and offered to support him, then returned to Haicheng to discuss Glutinous Rice Ball’s training progress with Zhao Wenyuan. Meanwhile, Zhang Chi arrived at Dingsheng Tower to hear a progress report from Liu Bo and Wang Hao.

  • Zhou Min revealed that she knew Han Luyi had been laid off and offered him her savings if his business failed.
  • Han Luyi met Zhao Wenyuan and learned that pre-training had stabilized, allowing the team to begin annealing.
  • Han Luyi explained annealing and directed Zhao Wenyuan to prepare evaluations for both foundational abilities and Source Code Technology’s product scenarios.
  • Zhao Wenyuan estimated annealing would take no more than five days, potentially advancing the start of post-training.
  • Zhang Chi arrived at Dingsheng Tower, met Liu Bo and Wang Hao, and asked them for a progress report.
Read chapter

Ch. 220Product positioning matters

Zhang Chi reviewed Liu Bo and Wang Hao’s unfinished coding-agent project and redirected it toward enterprise compliance and management rather than competing directly with Riding the Wind. He tasked them with improving the console and preparing a demonstration for Zheng Xiaobo, then invited Zheng to see the early product after the holiday.

  • Liu Bo and Wang Hao reported that the project was incomplete but had a working dashboard, basic coding workflow, and enterprise features such as permissions and operation auditing.
  • Liu Bo demonstrated the product to Zhang Chi, who identified the audit logs and enterprise management tools as its core value for compliance-focused customers.
  • Zhang Chi told Wang Hao to coordinate with sales on target customers and asked Liu Bo to refine the console and prepare a more complex demo for Zheng Xiaobo.
  • After Liu Bo and Wang Hao left relieved, Zhang Chi reflected that the team needed pressure and that the product should serve executives seeking compliance and reportable AI-efficiency gains.
  • Zhang Chi messaged Zheng Xiaobo to praise his foresight and arrange an in-person presentation of Dingsheng Cloud’s early enterprise-focused solution after the holiday.
  • Zhang Chi left the office, where employees were still working overtime, and headed home to rest.
Read chapter

Ch. 221Back to the Stone Age

Lin Yizhou struggled through his first day back at work without Riding the Wind, while Jiang Yixin reviewed the tool’s explosive public-beta growth and began planning for enterprise adoption. The chapter ended with Jiang discovering that Neus AI had announced an agentic programming tool.

  • Lin Yizhou found that his company prohibited Riding the Wind and struggled with the inferior company-approved AI coding tool, Qianyuan.
  • Jiang Yixin reviewed Riding the Wind’s rising registrations, daily users, and deeper project use, and concluded that it was becoming a trusted development tool.
  • Jiang Yixin read programmers’ complaints about companies refusing to approve Riding the Wind and recognized that enterprise compliance and procurement would be the next challenge.
  • Jiang Yixin drafted a Riding the Wind enterprise-edition access plan and then opened her accumulated AI news digest.
  • Jiang Yixin saw a headline announcing that Neus AI had released an agentic programming tool and suspected it had copied Riding the Wind.
Read chapter

Ch. 222Plagiarism, without a shred of shame

Jiang Yixin discovered that Neus had launched NeusAtlas by copying Riding the Wind and promoting it as the first software engineering agent. She identified the need to replace Neus’s Mercury Model and scheduled a meeting with Han Luyi to discuss migration plans and product risks.

  • Jiang Yixin watched Neus’s NeusAtlas demonstration and recognized that it copied the closed-beta version of Riding the Wind, including features shaped by the product’s testing problems.
  • Jiang Yixin reviewed Neus’s extensive publicity campaign and noted that its coverage repeatedly claimed Atlas was the first project-level software engineering agent.
  • Jiang Yixin reasoned that Neus’s move had turned the companies into direct competitors, making replacement of the Mercury Model urgent, and considered Source Intelligence’s Glutinous Rice Ball model.
  • Jiang Yixin went to Han Luyi’s office, where his new secretary Liu Huo asked her to send written materials and summarized the key decisions she wanted Han to make.
  • Liu Huo booked Jiang Yixin a half-hour meeting with Han Luyi at two that afternoon to discuss Glutinous Rice Ball’s progress, Neus cooperation, and configurable model providers.
Read chapter

Ch. 223Act before it arises, bring order before disorder begins

Jiang Yixin discussed Riding the Wind’s response to NeusAtlas and proposed making the product model-agnostic while Source Code Technology focused on domestic users. Zhao Wenyuan reported that Glutinous Rice Ball’s base model had achieved top-tier results, but Zhang Chi secretly obtained Han Luyi’s annotated data for Dingsheng and Cheng Yuan.

  • Jiang Yixin told Han Luyi that Source Code Technology should prioritize the domestic market instead of fighting NeusAtlas publicly, and Han Luyi agreed.
  • Jiang Yixin proposed decoupling Riding the Wind from specific models, and Han Luyi told her to make product-level decisions independently.
  • Han Luyi explained that Source Code Technology planned to build a Zhangjiakou data center to reduce costs and keep core data secure.
  • Zhao Wenyuan reported that Glutinous Rice Ball’s base model had benchmark results comparable to GPT-4, and Han Luyi ordered post-training to begin.
  • Zhang Chi learned that more than eighty thousand annotated entries had arrived, diverted them to himself on a USB drive, and told Cheng Yuan he had obtained the goods.
Read chapter

Ch. 224This Data Seems Off

Liu Dahai questioned the logic in the high-quality data Dingsheng received for training Kun Yuan, but Lin Shaofeng insisted training continue and moved to take him off the project. Meanwhile, Zhang Chi arranged to hinder Han Luyi’s training through Dingsheng Cloud, but Han Luyi documented the interference and forced Liu Yaguang to restore the resources.

  • After noticing that the annotations placed unusually strong emphasis on compliance, Liu Dahai asked Lin Shaofeng to suspend Kun Yuan’s training for a week, but Lin Shaofeng refused and planned to replace him with his deputy.
  • Lin Shaofeng asked Zhang Chi for more computing support, and Zhang Chi told Liu Yaguang to lower Han Luyi’s job priority and take nodes offline for maintenance.
  • Zhao Wenyuan reported the throttling to Han Luyi, who used Sight to identify the scheduling changes and submitted an urgent ticket with evidence of the interference.
  • After reading Han Luyi’s ticket, Liu Yaguang restored Source Intelligence’s job priority and brought the affected nodes back online.
  • Zhao Wenyuan saw that throughput had returned to normal, and Han Luyi told him to continue training before ending the call.
Read chapter

Ch. 225Probably Not the First

NeusAI’s Atlas beta drew widespread attention and helped CEO Ryan attract new investors, while marketing chief Michael attended a forum to promote Atlas as the first agent-based programming tool. A Google executive challenged that claim by pointing to SourceCode Technology’s earlier product, Yufeng.

  • Atlas’s beta release impressed testers and intensified debate about agent-based programming.
  • Ryan received renewed interest from existing and outside investors after Atlas’s launch.
  • Michael attended a San Francisco roundtable with Google’s Jason Chen and OpenAI’s Allen Kenny.
  • Michael called Atlas the first system to integrate agent-based programming and put it in users’ hands.
  • Jason asked Michael whether NeusAI knew that SourceCode Technology had released its Yufeng agent-programming product before Atlas.
Read chapter

Ch. 226What Is Yufeng?

Jason challenged NeusAI’s claim that Atlas was the first programming Agent, bringing attention to Yufeng’s earlier product, Riding the Wind, and the dispute went viral in China and overseas. Riding the Wind gained a surge of users as Jiang Yixin prepared enterprise pricing, while Han Luyi focused on Heavenly Craft’s final training and data center deployment before Sight leveled up.

  • Jason asked Michael whether NeusAI knew that Yufeng had launched Riding the Wind before Atlas, and Michael sidestepped the question by praising Mercury and their partnership with Yufeng.
  • The roundtable article went viral after its headline questioned whether Atlas was really first; Michael later issued a statement denying that NeusAI had promoted the claim.
  • Developers overseas and in China shared Riding the Wind’s launch timeline and reviews, driving public testing registrations toward two million and prompting enterprise clients to ask about a paid version.
  • Jiang Yixin drafted an initial enterprise pricing plan, using the one-way door/two-way door principle to justify setting the starting price high.
  • Han Luyi monitored Heavenly Craft’s final training and the data center deployment as Zhao Wenyuan estimated training would finish within days.
  • Sight leveled up before Han Luyi’s eyes.
Read chapter
Arc 9 of 21
AboutStatsAPIChangelogStatusContactPrivacyTermsDMCA
© 2026 RandomTranslator·v3.26·RSS