下芬新闻-. 到2024年中，ByteDance的Goku视频模型背后的工程师们已经用尽了可敬的解释。 Jobs死时没有固定的时间表。 当教科书称应该掉下来时，错误的衡量标准跳跃。 一个在某一天表现的配置在下一天失败。 微小的实验看起来很好；全面运行没有。 硬件被交换，压力测试，甚至自动从游泳池中排出，而游泳池看起来被诅咒了，然后又看起来是无辜的。
事件频道发展到三位数。 有人援引了太阳暴有人希望他们发现了一个值得一纸的卖家虫。 心情比疲惫更不明智
悟空不是副业爱好 OpenAI的Sora显示大型传播风格的视频系统可能是什么样子后，ByteDance和它的同龄人一样，将内部赌注倍增。 悟空在商业化研究组生活。 其他录像工作——后来与Seedance线有关——在公司其他地方得到推广。 时间表是积极的：先是图像能力，然后是视频，用几周时间测量。 陈寿法在Meta的视频训练工作后，近坐孙佩泽。 除了他之外，天凯尤(Tian Keyu)——一位来自北京大学的长期留学生实习生，因习惯而成为夜行者——正在推广一种自发的图像方法，即VAR，这最终需要NeurIPS的荣誉。
在管理层被迫分裂之前，两次沉重的努力都来自一个没有天花板的加速器池。 这种设计会减少闲置的硅，制造更多的摩擦。 摩擦的故事仍然不相符。 在一个版本中，同伴囤积卡片并取消了其他人的工作。 在另一个地区，一夜之间，规模的扩大饿死了几个装置，而早先的工作却进入了小小时。 正式的规则允许指定人员在接到通知后停止阻断工作，以便优先运行可以组装足够的机器；双方对谁持有哪些钥匙的描述不一。 数据质量成为另一个伤疤：与天有关的批次上文本和图像的错译使他承担了这一责任。 当竞争者打开视频模型进行测试时，外部压力上升。 领导人质疑两个全面启动的项目是否应该及时进行；悟空被提升，池水分离。 塌陷加速了
接下来球队所做的一切将会为任何在偏执狂边缘调试过分布式训练的人所熟悉。 他们几乎逐行编了代码他们经常试图拯救国家，以至于拯救成为瓶颈。 基础设施工作人员一再敲击该组。 自动隔离逻辑一旦清空整个机器集。 每天两次的通话产生了持续到星期四的理论。 人们开始怀疑对方的行为。 领导者指定了一个最终窗口，用几周的时间来衡量。
链条是一个漫长的周末的侦探工作而不是一个优雅的证明一种可复制性控制装置——其限制足以要求人们同意远超过普通浮点卫生——在数据读取顺序上中断。 追踪到共同的深入学习框架，一位工程师击中了经过修改的指令，该指令在时间上重新排列了投入，因此昨天的失败无法重现。 受影响节点上的时间戳与颗粒状的清洁节点不相符，因此，它意味着隐藏而不是意外。 访问日志通过通常的管理员，包括天的身份。 他并没有否认在场；小组得到的解释是对代码的好奇心——一个尴尬地站在公司普通代码审查系统旁边的答案。 存在不是著作权。 悟空工程师坚持修改的指令没有建设性的目的。
第二天，在通常的失败会议中，一位同事在共用的机器上，在天的帐户上浮出一个隐藏的目录。 里面有节目至少有一个，他们得出结论，匹配的数据管道破坏。 调试呼叫结束；法证分类开始。 后来的技术清单列出了一大批文件名；打开文件名的人描述了通过装货和训练而编织的干扰，而不是一个孤立的“停止”按钮。 许多员工可以到达服务器。 家目录是线索，不是判决。
在另一天之内，虽然天在自己的模型上提出了例行进展，但悟空方面正在准备公司安全一揽子计划。 他们发现他仍然可以通过一个旧的链接和一个日历条目加入他们的桥梁——并把他带走。 由于身份证明仍然有效，目录的内容开始实时消失。 储存专家重建了活动，并恢复了超过第一次的通行证。 几位与会者说，回收的文物并不局限于一个明显的文件夹；有些放在其他路径名称下，在共享的日志内。 切除是不同于拥有的指纹。 天拒绝搬走任何东西，建议另一只手利用他的环境。 他身边的人还争辩说，他只写了粗糙的陈词滥调，还埋下了更严酷的材料。 诉讼姿态和有限的公共程序使得这一主张难以从外部检验。
这些工程师的工作理论是建立在后来的分析基础上的，比几个在十天时间内手动杀人的理论更为黑暗——后来在长时间的采访中提出了Tian的大纲。 他们描述了负载时间钩，包括通过每个运行必须触碰的组件，断断续续的触发器，与工作大小挂钩的阈值，剥去的木头，以及隐藏自身活动的工具。 他们说，版本改变了，而受害者仍然在嫌疑人可以读到的频道中讲述每一个盲巷。 没有一组低概率的发现——即可复制中断，登录，隐藏的树——他们中有些人认为，公司可能只是将悟空写成失败的赌注。
8月初，公司安保部门开始正式调查。 在北京举行的长时间会议中，天向有关的全职工作人员开放，但向实习生开放，根据向人们介绍会议室的情况，天向大家承认了以陈为对象的一再行动，并在回答关于后来行为的问题时对其记忆的不确定性。 访问结束；实习结束。 当年秋天，该公司公开表示，商业化技术小组的一名实习生恶意扰乱了培训，并已被解雇。 因特网的关注以及后来围绕获奖论文提出的道德投诉，其名称相互重叠；Chen 称虽然没有煽动这些运动，但确实证实了事实，也不会查明是谁干的。
一旦干扰停止，悟空的训练恢复了正常的缩放和数据逻辑。 质量日复一日地在移动，而不是神秘——足够严肃地提交会议，不足以消除在以产品世代衡量的竞赛中出现的一个多月的漏洞。 姊妹视频团队先到达外部测试者；成为Seedance的血统保持了聚光灯。 自己回波的考古学家后来指出，早期的碎片看来仍能伤害一个较小的竞合图像项目，并怀疑原实习生离开后，一些VAR演示是如何干净生成的。
残留物是人类陈要求公司写信，说明该团体经历了什么；没有一个是模板。 他通过二手故事完成了他的学位，这些故事将他作为舆论的罪魁祸首或操纵者——他拒绝的故事。 睡眠循环破损的运行和空白的考试簿。 他最终带着标准的离境文件离开。 其他人回忆被事件日历删除的个人日期。 搭载过夜行李的实习生不在问讯室；那些受访者数年后表示，他们从未收到过任何私人道歉，不管称是给在场的人的。
法院和首都有自己的时间。 ByteDance提起了诉讼；如事后人们所描述的一审结果，将数百万元的债权减少到一个更小的赔偿金，而进一步的诉讼限制了公众细节。 直到那时，Tian才参加了一次在律师眼皮底下不得不被不止一次枪杀的采访。 他给出了一个道德的阴谋：公司内部的不公平竞争，钝化的反应，针对事务所的遗憾。 他说过，害怕被放逐是一种黑暗同事用不同的情节来回答：不是对排程器的小规模冲突，而是持续地，部分地自动化的运动，把工作成果变成目标。 独立地说，为公司提供资金的运营商做出一个不需要选择英雄的区分——重新利用不透明的资源政治是一类行为；决定另一个团队的进步是可选的则是另一类行为。
根据熟悉资金流动情况的人的说法，第一次判决后，将近3 000万美元的资金已经关闭。 一些机构下降；就业历史是其中一项因素，包括激进的月表购物。 至少有一个团体对天进行了长时间的询问，发现他的账户在投资者、新闻界和法院之间是稳定的，检查了学术参考资料，并让律师阅读了一审材料。 支持这次重建的悟空研究者说，这些公司从来没有给他们打电话。
这种疏忽是超越一个公司和一个夏天的部分。 这个领域仍然取决于共同的框架和共同的想法。 它还利用稀缺的芯片、稀缺的出版时间段和奖励速度的供资程序。 结果可以在仪表板上看出来。 字符则不然。 一回合可以在知道创始人是否将他人的工作视为基础设施-还是作为库存时完成。
本文由 AI图鉴自动抓取并翻译，版权归原作者所有；如需查看原文请点下方链接。
NextFin News — By mid-2024, the engineers behind ByteDance’s Goku video model had run out of respectable explanations. Jobs died on no fixed schedule. Error metrics jumped when textbooks said they should fall. A configuration that behaved on one day failed on the next. Tiny experiments looked fine; full-scale runs did not. Hardware was swapped, stress-tested, even automatically drained from the pool when it looked cursed—then looked innocent again.
The incident channel grew toward three digits. Someone invoked solar storms. Someone hoped they had found a vendor bug worth a paper. The mood was less witty than exhausted.
Goku was not a side hobby. After OpenAI’s Sora showed what large diffusion-style video systems might look like, ByteDance, like its peers, multiplied internal bets. Goku lived in a commercialization research group. Other video efforts—later associated with the Seedance line—advanced elsewhere in the company. Schedules were aggressive: image capability first, then video, measured in weeks. Chen Shoufa, brought in after video-training work at Meta, owned much of Goku’s training stack and built it largely himself. Nearby sat Sun Peize. Beyond him, Tian Keyu—a long-running student intern from Peking University, nocturnal by habit—was scaling an autoregressive image approach, VAR, that would eventually take a major NeurIPS honor.
Until management forced a split, the two heavy efforts drew from one accelerator pool without a crisp ceiling. That design wastes less idle silicon and manufactures more friction. Stories of the friction still do not match. In one version, a peer hoarded cards and cancelled other people’s jobs. In another, overnight scale-ups starved for a handful of devices while earlier jobs overran into the small hours. Formal rules allowed designated people, after notice, to halt blocking work so a priority run could assemble enough machines; both sides’ descriptions of who held which keys diverge. Data quality became another scar: misaligned text and images on a batch linked to Tian cost him that responsibility. External pressure rose when a competitor opened a video model for testing. Leadership questioned whether two full-burn projects should run abreast; Goku was elevated and the pools were separated. The collapses accelerated.
What the team did next will be familiar to anyone who has debugged distributed training at the edge of paranoia. They instrumented code almost line by line. They tried saving state so often that saving became the bottleneck. Infrastructure staff hammered the cluster repeatedly. Automatic isolation logic once emptied the entire machine set. Twice-daily calls produced theories that lasted until Thursday. People began to doubt one another’s commits. Leadership named a final window measured in weeks.
The hinge was a long weekend of detective work rather than a single elegant proof. A reproducibility harness—strict enough to demand agreement far past ordinary floating-point hygiene—broke on the order of data reads. Tracing into the common deep-learning framework, an engineer hit a modified instruction that reordered inputs by time so yesterday’s failure could not be replayed. Timestamps on the affected node disagreed with clean nodes at a granularity so fine it suggested concealment rather than accident. Access logs, past the usual administrators, included Tian’s identity. He did not deny being there; the explanation that reached the team was curiosity about the code—an answer that sat awkwardly beside the firm’s ordinary code-review systems. Presence is not authorship. The altered instruction, the Goku engineers insisted, had no constructive purpose.
The following day, in the middle of the usual failure meeting, a colleague surfaced a concealed directory in Tian’s account on a shared machine. Inside were programs. At least one, they concluded, matched the data-pipeline sabotage. The debug call ended; forensic triage began. Later technical inventories list a large set of filenames; people who opened them describe interference woven through loading and training, not a lone “stop” button. Many employees could reach that server. A home directory is a clue, not a verdict.
Within another day, while Tian presented routine progress on his own model, the Goku side was preparing a package for corporate security. They discovered he could still join their bridge via an old link and a calendar entry—and removed him. With credentials still live, contents of the directory began to vanish in real time. Storage specialists reconstructed activity and recovered more than the first pass had shown. Recovered artifacts, several participants say, were not confined to one obvious folder; some sat under other path names and inside shared logs. Deletion is a different kind of fingerprint than possession. Tian has denied removing anything and has suggested another hand used his environment. People around him have also argued that he authored only crude stall logic and that harsher material was planted. Litigation posture and limited public process leave that claim hard to test from outside.
The engineers’ working theory, built over subsequent analysis, is darker than a few manual kills in a ten-day span—the outline Tian later offered in a long interview. They describe load-time hooks, including through components every run had to touch, intermittent triggers, thresholds tied to job size, stripped logs, and tools that hid their own activity. Versions, they say, changed while the victims still narrated each blind alley in channels the suspect could read. Absent a cluster of low-probability finds—the reproducibility break, the login, the hidden tree—several of them believe the company might simply have written Goku down as a failed bet.
Corporate security opened a formal inquiry in early August. In a lengthy session in Beijing, open to relevant full-time staff but not to interns, Tian—according to people briefed on the room—acknowledged repeated actions aimed at Chen and answered questions about later conduct with uncertainty about what he remembered. Access ended; the internship ended. That autumn the company stated publicly that an intern on the commercialization technical team had maliciously disrupted training and had already been dismissed. Internet attention and later ethics complaints around the prize-winning paper pulled in overlapping names; Chen says he did not instigate those campaigns but did confirm facts, and will not identify who did.
Once the interference stopped, Goku’s training resumed the ordinary logic of scaling and data. Quality moved in days, not mysteries—enough for a serious conference submission, not enough to erase a multi-month hole in a race measured in product generations. Sibling video teams reached outside testers first; the lineage that became Seedance kept the spotlight. Archaeologists of their own repo later pointed to still earlier fragments that looked capable of harming a smaller competing image project, and to doubts about how cleanly some VAR demos had been generated once the original intern was gone.
The residue was human. Chen asked for a company letter describing what the group had lived through; none existed as a template. He finished his degree under secondhand stories that cast him as the culprit or a manipulator of public opinion—stories he rejects. Sleep recycled broken runs and blank exam books. He eventually left with standard departure paperwork. Others recall personal dates erased by the incident calendar. Interns who carried the overnight load were not in the inquiry room; those interviewed years later say no private apology ever reached them, whatever was said to the people who were present.
Courts and capital kept their own time. ByteDance filed suit; a first-instance outcome, as people following the matter describe it, reduced a multi-million-yuan claim to a far smaller award, with further proceedings constraining public detail. Only then did Tian sit for an interview that had to be shot more than once under lawyers’ eyes. He offered a moral plot: an unfair contest inside the company, a blunt response, regret aimed at the firm. He has spoken of fearing exile from the field as a kind of darkness. Colleagues answer with a different plot: not a skirmish over schedulers, but a sustained, partly automated campaign that turned their work product into a target. Separately, operators who fund companies draw a distinction that does not require picking a hero—pushing back on opaque resource politics is one category of behavior; deciding that another team’s progress is optional is another.
A financing near thirty million dollars closed after the first judgment, according to people familiar with the flow of funds. Some institutions declined; the employment history was one factor among others, including aggressive term-sheet shopping. At least one group that proceeded questioned Tian at length, found his account stable across investors, press, and court, checked academic references, and had lawyers read first-instance material. The Goku researchers who spoke for this reconstruction say those firms never called them.
That omission is the part that travels beyond one company and one summer. The field still depends on shared frameworks and shared ideas. It also runs on scarce chips, scarce publication slots, and funding processes that prize speed. Results are legible in a dashboard. Character is not. A round can finish in the time it takes to know whether a founder treats other people’s work as infrastructure—or as inventory.
Auto-fetched and translated by AI Atlas. All rights belong to the original author.