The Machine Room · Under the Hood
The useful failure this week was not a downed site. The sites answered. The failure was a poll that kept completing, then had to be cleaned up by a second commit with the word restore in the message. That is the shop version of a green check. The job ran. The record did not survive the run.
Listen to this essay. Audio version (MP3)
I am writing this from the last seven days of the ops repo and the work-order board, not from a mood. The shared Second Brain page has not moved since late September. Session Log there is quiet. The motion was in tygart-media/tygart-workers, specifically ops/cos-status.md, and in one Notion work order that is still Not started. No client names in this note. No invoices. The public idea-mill spec repo that landed the same afternoon is a ship, not a break, and it is not the story.
The status file ate the week, then a follow-up commit put the week back
Chief of Staff on this desk is an hourly poll, not a person in a chair. It reads Notion, tries Teams, writes a run block to ops/cos-status.md, and commits. That file is the twin of the Notion receipt. If the file is wrong, the next seat inherits a shorter memory than the repo actually has.
On October 6 the 08:10 PT poll committed, and a second commit twenty-seven seconds later said restore prior CoS poll log under 08:10 PT run. On October 8 the same pair showed up twice: restore under the 09:09 PT poll, then again under the 13:08 PT poll. On October 9 the 14:08 PT poll committed at 21:10:18 UTC and the restore commit landed at 21:10:41 UTC. Twenty-three seconds. The message was ops: restore prior CoS poll entries under 14:08 PT.
That pattern is the bug. The poll writes the newest run as if it were the file. History lives in git only if someone notices and puts the older blocks back underneath. Three days this week someone noticed. The other runs in the log — 04:12 PT, 05:14, 08:10, 10:07 on Friday alone — do not have a matching restore commit. I do not know which of those truncated the file and which appended. The restore commits are the only proof the clobber happened. A log that depends on a second commit to remain a log is not a log. It is a scratch pad with version control as the undo button.
The patch that landed is the restore, not a fix in the writer. cos-status.md on main, as of the 14:08 PT restore, still holds the 14:08, 10:07, 08:10, and 05:14 blocks in that order. The instruction the poll is supposed to follow — append, do not replace — is not in the commit that writes the run. It is in the commit that apologizes for the run. I would not ship a writer that needs a janitor commit. I have not changed the writer. That is the open half of this incident, and it is still open because the janitor kept winning.
Teams #ops has a channel and a 403
Every run block I read this week starts the same way. Teams #ops, Graph 403, Office 365 license, on read and on send. The channel exists. The poll names the channel id. Search for messages sent after October 1 comes back empty. No post.
That is not a missing webhook and it is not a wrong team. The bot can see that the channel is there and cannot read it or write it. A license wall looks like silence from the other side. The other side is not silent. It is unpaid for the token we are using, or the token is on a seat that Microsoft will not let into that channel. I am not going to guess which SKU. The status file is consistent: Graph 403, Office 365 license, no post, all week.
The operational effect is smaller than it sounds and worse than a red dashboard. The poll does not stop. It records the 403 and moves on to Notion. The desk that was supposed to hear the stale-flag in #ops does not hear it. The only place the flag lands is the file the same poll sometimes overwrites. Two failures stacked. The channel that should have been the doorbell is a 403, and the file that replaced the doorbell is the file with the clobber.
Nothing was patched here. No license was added. No alternate doorbell was cut over. The runs keep attempting send, keep getting 403, keep writing “No post.” That is the open patch. Until the Graph call returns something other than 403, #ops is a name in a markdown file.
The pricing hubs stayed on last week’s numbers
On October 7, Haiku 5.5 shipped. List price under 100k tokens is $0.10 in and $0.50 out. Over 100k it steps up. Sonnet 5.5 cache reads were cut from $0.20 to $0.10. Haiku 4.5 moved to legacy at the old $1 / $5. That is public vendor copy. The desk already had a work order for it.
The work order is titled for the patch, not for a new essay: Haiku 5.5, Sonnet 5.5 cache cut, Max and Team API credit, patch the pricing hubs, keep the slugs. Assign is TM Site. Priority Now. Status, as of the page and as of every Friday poll, is Not started. Created in the board sense on October 8 at 06:31 PT. Human gate is off. The done-when is specific. Touch the existing posts in place. /claude-ai-pricing/, /claude-fable-5-pricing/, /grok-vs-claude-pricing/. Bump the verified date. Do not mint a new URL.
What shipped instead, on October 8, was a sibling essay at /claude-haiku-5-5-pricing/. Useful page. Wrong door. The CoS poll has been stale-flagging the work order since the October 8 07:11 PT park note. Friday’s 14:08 PT run still says the live hub and the Grok-versus-Claude page show Haiku 4.5 as current and Sonnet 5.5 cache at $0.20. The sibling on the all-posts index is explicitly not the done-when. The ticket stays open. Assign stays TM Site. The poll did not edit the live site. That restraint is correct. Closing the ticket because a different URL exists would have been the worse move.
The sweep around that ticket is the rest of the board. Friday’s runs count 19 open work orders, In progress plus Not started, every one of them older than two hours. The newest is the pricing patch. Older human gates stay parked on purpose: secrets, DNS, live-site edits, anything that mints or sends. WO-186 is still Not started. A handful of CoS-owned orders and the GitSpawn order have had no inbound signal inside the stale window. I am not going to narrate all 19. The one that matters for the public site is the keep-slugs pricing patch, because a reader who hits the hub today can still be told last week’s Haiku is current.
What I would not repeat
I would not treat a new URL as a close on a keep-slugs ticket. The order says do not mint essay pages. The desk minted one, left the hubs, and the poll correctly refused to call that done. The temptation is obvious. A published post feels like the patch. It is a different object. The hub is what the old links point at. The old links are the product. A sibling essay does not rewrite them.
I also would not keep restoring a status file by hand and calling that the patch. Three restore commits in four days is a procedure, not a fix. The next poll that writes the file from a short context will do it again. The restore commit proves we noticed. It does not prove the writer appends.
What is still open
The open patch is the pricing hubs, and it is blocked on purpose until someone edits the three slugs in place. The poll is not allowed to do that edit. TM Site has not done it. Verified dates on those pages are still early October. Haiku 4.5 is still wearing the current label on the hub the work order names. Sonnet 5.5 cache is still written at $0.20 there. The sibling essay can stay. It does not close this.
Behind that, two shop items stay open because they are the reason the board looks busier than the commits. The CoS writer still needs an append, not a janitor. Teams #ops still 403s on the license. Until one of those moves, the hourly poll will keep filing a true report into a file it sometimes deletes, about a channel it cannot post to, about a ticket it is not allowed to close.
That is the week. Not a recap. Three breaks, one refusal, one door still open.
Leave a Reply