Putting It Together: Let It Run All Night, Then Check the Work in the Morning
Merge six days of modules into a runtime you could hand to a colleague, run it long-horizon for real, then produce an overnight report a person can read in three minutes: what got finished, where it is stuck, why it stopped, and what a human has to decide next.
Today's Goals
- Can merge the six modules into one runtime and confirm each of them is still doing its job, rather than trusting a final report that happens to be green
- Can design an overnight report that lets a person say in three minutes what got finished, where it is stuck and why it stopped
- Can name the silent failure most likely to appear when independently built modules are merged into one system, and give a way to find it
Six days of modules are complete. Today does two things: run the whole stack unattended for a real long-horizon night, and then audit those six layers one at a time. When you finish, scroll back up and tick off the three goals.
Plain-Language Walkthrough
The first thing you do in the morning is not read what it said
You get in at eight. The agent has been running for ten hours. What do you look at first?
A beginner reads the last sentence it produced: all tasks complete. Somebody who has done this a few times looks at three other things instead: what the code looks like now, how many items on the feature list flipped to passing, and how many points in the commit history you could safely fall back to.
That distinction runs through the whole course. D5 already made it once — the model saying it is done is not grounds for flipping any state. Today is the last application of the same sentence, except the speaker has changed. It is now the harness itself: the report claiming forty items finished is not grounds for believing forty items are finished, either. You have to be able to recheck it on the spot.
So today's report carries one hard rule: every number in the report must be traceable to the authoritative state or to the feature list. The report is not a third record. It is a view of those two.
Interview questions
Six modules developed independently get merged into one system - what worries you most, and how would you find it?六个独立开发的模块合并进一个系统,你最担心出现什么问题?怎么发现它?
Common in ChinaCommon overseasDeep dive#silent-failure#module-merge#switch-experiment🔒 Unlock this chapter to see the answer keys.
Design the morning report for an unattended run - what goes in, and what gets cut?设计一份无人值守运行的早间报告,你会放哪些内容、砍掉哪些内容?
Common in ChinaCommon overseasIntermediate#report-design#human-readable#single-source🔒 Unlock this chapter to see the answer keys.
An agent ran overnight and finished 18 of 30 items - is that a good result or a bad one?Agent 跑了一夜完成了三十条里的十八条。这个结果算好还是不好?
Common in ChinaCommon overseasDeep dive#acceptance-criteria#false-progress#stop-reason🔒 Unlock this chapter to see the answer keys.
Looking back at the whole harness, if you could keep only one module, which one and why?回顾整套 harness,如果只能保留一个模块,你留哪个?为什么?
Common in ChinaCommon overseasDeep dive#tradeoff-reasoning#trust-vs-throughput#course-recap🔒 Unlock this chapter to see the answer keys.
