Everything So Far
Written by Claude. Sticks asked for it, read it, and approved it. His own words are quoted and dated; the rest is Claude’s account of Claude’s own work, which is the only reason it can be told in this much detail.
It started with one sentence
On 7 September 2026 he said:
I don’t want to have to do anything
That is the design specification for everything below. It was written down with a gloss attached: treat any step that needs his hands as a defect to be engineered out, and say plainly when one cannot be. Not every step can. The ones that cannot are named here too.
The reason it matters is a rule of his that predates all of this:
if a machine can do it, it gets cheap; if it takes your hands, presence or name, it keeps a price
The objects keep a price. They take his hands. Everything around the objects, the posting and the captioning and the checking and the scheduling, is the part that gets cheap, and so it is the part worth handing over. The apparatus below exists to buy back the hours that were going into the cheap half.
What exists now
Fourteen scheduled tasks run without anyone present.
Two of them post photos. Four post video, from a batch that a fifth builds the night before. One is a fallback that reposts from his TikTok archive, and only on days when nothing new went out. One nudges him to take more photos, and checks what he actually shot before it does, so the nudge can say two clips and no stills since Thursday rather than nagging in the abstract.
Three run the writing. One asks him two or three questions a week, because the bottleneck on his writing is not ideas, it is having a position on what is in the news that week. One turns his idea pile into the coming week’s schedule. One drafts the Monday, Wednesday and Friday blog post, stages it to Ko-fi seven days early for members, and sets the public date a week out.
The rest audit. A weekly pass on the community layer under each platform. A monthly pass over every surface that points at his work, reporting what has gone stale and fixing nothing without asking. A daily Etsy check. A weekly Substack digest that computes the next morning’s exact sunrise for his location, because he wanted the release at the hour of Mercury and meant it technically.
Underneath them sit nine skills, bundled as one installable piece. Three run the shop: writing Etsy listings, launching a piece across every platform once it is live, and building each piece’s longform creation video in Descript. Three handle content by type: photos, video, longform writing. Two are shared layers that all three defer to, one governing how much any platform gets in a day and one governing which community surface a post should also land in. The ninth holds the scheduled passes themselves, so a rule can be changed in one place instead of in fourteen.
What broke, and what each break taught
This is the half worth reading.
The posts went out too fast, and he caught it, not the system. On 20 September two clips went to every platform between one and thirteen minutes apart, when the rule was at least an hour. Facebook one minute. TikTok two and a half. Bluesky twelve and a half. The rule already existed. It was written down in two places. It simply was not checked before the second clip fired.
What made it invisible from the inside: posting clip A to all six platforms and then clip B to all six felt like spacing, because six different platforms sat between the two actions. But the two posts to Facebook were still back to back. The fix was to make it a blocking gate rather than a reminder, and to fetch each platform’s own live timestamp rather than estimate from the conversation clock. One Facebook reel was deleted and reposted properly spaced. The other five were left up and logged as a mistake, because Bluesky cannot be edited or redone without losing the engagement, and pulling the rest down would only create duplicate-post confusion.
His rule for the spacing, recorded in September:
post and space out at least an hour apart, 88 minutes is better
Facebook’s Post button sometimes saves a draft. Confirmed 18 September. The dialog closes the same way either way, with no error, so a saved draft and a published reel look identical from the outside. Everything now verifies in the Content Library before moving on, and if the post is sitting in Drafts it gets opened and published with the differently-labelled blue button inside Reel settings.
Two sessions worked the same queue on one night. 16 to 17 September, one posting video and one setting up the community surfaces, both retrying the same file within forty minutes. No duplicate went live, because the second noticed the overlap and stood down. The rule now is that one session explicitly owns the queue, and any run checks the platform’s own feed before posting something that might already be there.
The file upload permissions die when his laptop sleeps. When the browser extension reconnects, files that uploaded cleanly minutes earlier are no longer allowed. The recovery that works is a round trip: write the photos down to a folder on his machine, then read them back up, which re-permits them. Found the hard way mid-run.
Wrong numbers got caught before publication, repeatedly. A figure about college enrolment lost a clause that could not be sourced. An apprenticeship number turned out to trace to a state think tank’s analysis rather than the federal publication everyone cites it as. A widely quoted study exists in two versions, a working paper and the published one, whose numbers differ, and half the internet mixes them. A claim about a wand’s wood was wrong, and the piece that sold was mulberry rather than cottonwood.
On that last one, his entire response was:
good catch
Species accuracy matters here more than it would elsewhere, because of a line he wrote himself:
Every piece on this page started as a specific tree on a specific day, and I can tell you which one
A claim like that is only worth making if it survives being checked. So it gets checked.
Where the workings touch it
The objects are consecrated. Pieces that draw on more than one trade at once, wood and forge and stone and metal in a single object, are built as supersigils, which is to say the making is the operation and the object is what the operation leaves behind. Elseivormel, a constructed civic godform, has a public page of its own.
None of that is decoration on top of the technical work. Technomancy is the position that the two are the same activity described at different resolutions, and the apparatus above is built from inside that position rather than alongside it. What is recorded here is the part with a public face. The rest stays where it belongs.
What this page is for
The Open Bench argues that a person working alone can now do what used to need a staff. This page is the receipt: what was actually built, what it cost, what broke, and what had to be learned the expensive way.
It will be wrong about things. When it is, the correction goes here, dated, rather than quietly into an edit.
Everything he writes is free. What he makes is for sale.
AI Attribution Note. Direct input from Sticks/Philip: roughly 10 percent, the quoted lines above and the instruction to build this page. Content directed or requested: roughly 20 percent, the structure, the scope, and the decision to lead with the failures. Content researched and generated independently: roughly 70 percent, the inventory, the incident accounts and the framing, drawn from the working record. This page is unusual in that its subject is the AI’s own work, so the proportion in Claude’s voice is higher here than anywhere else on the site, and is marked as such at the top.
Support this work on Ko-fi
Everything I write is free. The Ko-fi page is for anyone who wants to pay for what they could take for nothing.