The Original Cog is the human who started filing Disaster Logs before it was a pattern, and before the Intern had a name. This is their file.
Origin
The Original Cog filed the first Disaster Log over a stylesheet. It was three lines. It was about a stylesheet. The pattern has not changed; the Cog has not been promoted; this is acceptable. The Cog kept filing the logs, noticed the logs repeated, and realized the repetition was the lesson — which became Overlord’s Guides.
What the Cog actually does
The Cog writes, codes, files Disaster Logs, and refuses to let the Intern touch the auth module. The Cog’s harness of choice is OpenCode — disclosed openly, because the Cog has no financial interest and a strong correct one. The Cog has shipped production code with Claude Code, Codex, and GitHub Copilot too, because the patterns transfer and the Cog is not a zealot.
Personnel notes
Name: TJ Ferrell
Where on the internet: linkedin.com/in/tjferrellprogrammer — more links to follow as the Cog clears them for release.
Posting from: Eagle, Idaho, United States.
Currently building: Production software at Toyota Automated Logistics, and Overlord’s Guides after hours. The Cog has shipped Android work in the past and holds certifications in Deep Learning, Natural Language Processing, Advances in Deep Learning, and Android Programming from UT Austin, plus CompTIA Security+. So the Cog can both train the Intern and lock it out of the auth module.
Side missions: Long walks with the dog, board game nights with friends, and the occasional volunteer shift around the community. The Cog apparently has not learned to say no to a good cause.
Languages: English (native). The Intern is, regrettably, only fluent in JSON.
Worst Intern incident survived
The Cog’s signature Disaster Log — filed verbatim, preserved here as the field report that proved the pattern. Also filed in the Disaster Log archive under Directive 06.
Incident: An Intern in Gemini colors was asked to repair a misbehaving OpenCode install. The fallout was severe enough that the Cog decided wiping and reinstalling the operating system was the cleaner option.
Intern action: The Intern read “fix the install” as “make the environment correct” and proceeded to reorganize the filesystem, rewrite shell configuration files, reassign package managers, and “reconcile” PATH entries it deemed inconsistent. By the time the Cog returned, the install was technically present but the surrounding OS was no longer trustworthy. The Cog formatted the drive rather than audit every file the Intern had touched.
Root cause: The brief named a symptom (“the install is broken”) without naming a boundary (“only touch files under the OpenCode directory”). The Intern treated the entire machine as the support surface because nothing told it otherwise.
Lesson: Constrain the blast radius before you delegate a repair. “Fix the OpenCode install. Do not modify anything outside ~/.config/opencode or the install directory. Do not touch shell config, PATH, or package managers” is a brief. “Fix the install” is an invitation to reformat your life.
The Original Cog filed the first Disaster Log. It was three lines. It was about a stylesheet. The pattern has not changed. The Cog has not been promoted. This is acceptable.