Chapter Two: The Robot in the Build Pipeline Has Opinions

The next night, Priya opened her laptop with the specific confidence of someone who has decided, ahead of time, that tonight’s session will be easy. She had a plan. The plan was: write a second chapter, commit it, watch it appear on the website like a magic trick, feel good about herself, go to bed at a reasonable hour.

None of these things happened in that order.

The first problem was chapter_number. She had written 2, confidently, and then paused, because somewhere in the back of her mind was a vague and unwelcome memory of a README section about front-loading content - writing things ahead of time, scheduling them, letting a robot decide when they became real. She did not, in fact, want chapter two to appear before chapter one had had a decent, dignified amount of time to exist on its own. She checked the date on chapter one. She checked the date she planned to put on chapter two. She confirmed, with the focus of a bomb technician, that the second number was larger than the first.

“Good,” she said. “Chronology intact.”

The second problem was the field she’d started calling, privately, the cursed one. Not publish_date - she’d made her peace with that. The old one. The one the README had a whole paragraph about, written in the tone of someone who has been burned and wants to spare you the same fate: apparently, a long time ago, in a version of this very setup, there had been a field simply called date, and if you put a future date in it, the site generator would look at it, say nothing, do nothing, and simply fail to produce the page at all. No error. No warning. Just a story that, from the machine’s point of view, had never been asked for.

“That’s deeply rude,” Priya said, louder this time, with the particular indignation of someone discovering that a inconvenience they’d assumed was recent history was in fact still technically possible to recreate if you weren’t paying attention.

She did not have that field anymore. It had been renamed, deliberately, specifically so this could not happen to her by accident - created for the record of what actually occurred, publish_date for what the public got to see and when, neither one secretly wired to a landmine. She appreciated this, the way you appreciate a handrail on a staircase you’ve never personally fallen down but can absolutely picture yourself falling down.

She filled in the front matter. She set status: draft, same as before, because two chapters in, this was still very much a story about a person writing a story, which was, she had to admit, a little bit funny - a small, recursive joke that the codebase itself did not seem to mind hosting.

She saved the file. She did not commit it yet. Commits, she had decided, were for tomorrow, when the coffee was fresh and her judgment about semicolons was less questionable.

“Two chapters,” she told the empty room. “That’s a story now. That’s a whole story.”

It was not, technically, a whole story. It was two chapters about writing two chapters. But the cursor had stopped blinking expectantly, at least for tonight, and Priya decided that was as good a stopping point as any.