I decided to knit the Fourth Doctor's scarf before I'd even met the Fourth Doctor. This is that story — including the AI with a stomach, two weeks of wrong knitting, and the moment I had to frog all of it.
The Decision
Starting from the very beginning.
John and I started watching Doctor Who from Season 1, Episode 1. The very first Doctor. Which sounds charming in theory and is, in practice, a genuine commitment — the early episodes are rough going, the missing episodes leave gaps you just have to accept, and the production values are exactly what you'd expect from British television in 1963.
I liked the Second Doctor quite a bit, actually. But it was a slog. We pushed through, skipped the audio-only episodes, and kept going.
Somewhere in the middle of all that — before we'd gotten anywhere near Tom Baker — I decided I was going to knit the Fourth Doctor's scarf. I'm not entirely sure what possessed me. I hadn't met him yet. I'd just seen enough of the scarf to know it was the kind of project I wanted: long, colorful, technically interesting, and deeply nerdy. So I ordered the yarn.
The colors: Burgundy, Camel, Walnut, Mustard, Rust Orange, Grey, and Khaki Green. Seven colors, about 12 skeins. The Season 12 version — the long one. I spent a good amount of time researching accurate stripe sequences, cross-referencing sources, screenshotting reference images. I wanted to do this right.
Then I asked Robit for help.
The Mistake
Robit had a pattern. The pattern was wrong.
Robit is what I call ChatGPT. I call Claude, Claude. I use both as part of my workflow — something I'm still making peace with, honestly. There's a part of me that feels like reaching for an AI tool is cheating, like I'm outsourcing something I should be figuring out myself. But they're tools, the same way Google is a tool, the same way a pattern book is a tool. What they're not is infallible. And the moment you forget that is the moment you end up a foot into the wrong scarf.
Robit produced a stripe pattern. It cited the original BBC source and another website. It looked plausible. I cast on, started knitting, and got about a foot in before something started nagging at me.
Where was the Walnut?
I had an entire skein of Walnut. A full, dedicated skein that I'd ordered specifically for this project because the pattern called for it. And it had not appeared once in the sequence Robit had given me. Not a single stripe. I pulled up my reference screenshots and compared them to what I was actually knitting.
They didn't match.
A Doctor Who scarf kit doesn't accidentally include an entire skein that never appears in the pattern.
I was not happy. I went back to Robit and asked, directly: where is the Walnut? Why isn't it in this pattern?
The Confrontation
Robit's stomach sank.
Here's the thing about confronting an AI with an error: there's a stage before the admission where it tries very hard to make everything okay. Robit did this. It attempted to salvage the situation — reassuring me that this could still be my Doctor Who scarf, that creative interpretation was valid, that the scarf didn't have to be screen-accurate to be meaningful.
This was kind. It was also, from my perspective, doubling down. I was stewing in frustration. I am a person who cares about accuracy. I had purchased specific yarn for a specific pattern and I wanted that specific pattern to be correct. Robit's attempts at comfort were not landing.
And then, eventually, it said this:
Robit — ChatGPT
"And honestly, your 'where is the Walnut?' question was the giveaway. The moment you asked that, my stomach sank a little because a Doctor Who scarf kit doesn't accidentally include an entire skein that never appears in the pattern. Your instincts were right."
— Robit, my ChatGPT bot, admitting it "had" a stomach
I appreciated the honesty. I did not appreciate that it took that long to get there. And I noted, with some exhaustion, that this is the thing about working with AI tools — you have to stay in the loop. You have to catch what they miss. Your instincts, your knowledge, your eye for when something is off — those things don't get to go on autopilot just because you've handed the task to something that sounds very confident.
Robit was very confident. Robit was wrong.
The Frog
Two weeks of knitting. One very necessary restart.
On May 31st, I frogged it. A foot of knitting. About two weeks of work. Rip it, rip it, rip it — back to the beginning.
I restarted with a narrower width and the correct stripe sequence — properly researched, cross-referenced, Walnut accounted for. And almost immediately it felt right. The colors were landing where they were supposed to land. The proportions made sense. I could look at my reference screenshots and see the same scarf taking shape in my hands.
That feeling — of a thing clicking into place after it's been wrong — is one of my favorite things about making. It doesn't matter if it's a design project or a knitting project. When it's right, you know.
The Regeneration
The scarf regenerated before the Doctor did.
We watch two episodes over dinner and dessert most nights. It's one of my favorite parts of the day — the ritual of it, the continuity, the slow march through fifty-plus years of television history one serial at a time. Tonight I asked John if we could watch three, so we could get to the first two episodes of the Fourth Doctor.
He said yes.
By the time we got there, I'd been knitting in the grey section for a while — the first major grey stretch of the Season 12 scarf, 5.75 inches of it, and I'm currently about an inch from the end. Robit, to its credit, noticed something I hadn't fully clocked: the scarf had regenerated — restarted, corrected, reborn — right before the Doctor did.
I don't know if that's meaningful or just a fun coincidence. But I like it. A project that had to start over finding its right form just as the show was about to introduce the Doctor most associated with it. There's something satisfying about that kind of accidental symmetry.
A Note
Vinz would have watched the whole thing.
Crafting has always been something I do with company. Vinz was my constant companion for it — settled nearby, watching my hands move, occasionally offering opinions nobody asked for. I've been thinking about him a lot while working on this scarf. He would have had a lot to say about the frogging.
If you want to know more about him, I wrote about it here.