Weekly Reflection for Week 41 2026

Week 41 runs Sunday 2026-10-04 through Saturday 2026-10-10. The day headings below carry their dates.

The companion piece is Stimpunks.org Changelog for Week 41 2026: From the Kitchen to the Pub, From the Source to the Page, which records what shipped. This one records what it cost.

Best Accomplishments

Stimpunks.World got somewhere to eat, drink, and sit down, and every seat in it can be reached. Hey, Good Cookin’ is a community kitchen where nobody is turned away. Pekoe and Purrs is a cat café where every cat is waiting at a shelter for a home. Brew and Stew is a woodland tea room lit by foxfire. A Quiet Pint is a pub under the street, and its player piano plays rolls that Scott Joplin and Alexander Scriabin played onto the paper themselves. Four lots opened where the buildings stop: the Run, the Truck Stop, the Green, and the Pile. The 2010 ADA Standards ask for one accessible seat in twenty. In the kitchen every seat is one, and the pub’s tool refuses any table without a way to it 36 inches wide.

People told us they were having a hard time finding each other, and the street answered. The CB gained Who’s online, and the privacy page says which two of Ryan’s written rules it reversed, and the date it reversed them. Calls in every room began working in Chrome, after our own security header had kept them from the camera, microphone, and screen under a rule written down on 28 September. And on Saturday a second guest’s room arrived: Words, Bud, Beats, a salon at desert dusk by Kristina Brooke, with one line changed on the way in and TIDAL players that any future guest room can carry.

Our EspoCRM trial learned to send, and now remembers back to October 2021. On Monday our team address began sending from inside EspoCRM, and an AI assistant connection went in that cannot delete, export, or send anything. On Wednesday and Thursday the trial took in about 16,700 emails from the team mailbox, each linked to its contact wherever the address matched. Auto-reply was confirmed off on every account before anything ran, and no auto-reply went out.

On stimpunks.org we published Brand Voice: How We Sound and Why, and had to fix our own Style Guide first. Its Punctuation page told writers to put no spaces around em-dashes, against 3,595 spaced dashes in our posts since July. We also removed a one-character limit from 28 answer fields on three live governance forms, and wrote the Campfire post for Maya Angelou and James Baldwin.

Alongside them, the CB got a guide to every control and the street a page on how it runs. The Events Room got a shared screen and a lift, the Green a daily rack about cities making room for green, and Swaying Sweetgrass the start of Braiding Sweetgrass in Robin Wall Kimmerer’s own voice. Four posts reached stimpunks.org as blocks that WordPress’s Markdown converter never touched.

Theme

Every day we worked this week turned up a fault that had been quiet until then. On Sunday a search result stopped short of the three rooms it needed, and nothing in the output said so. On Monday the kitchens’ allergen engine had been telling three bánh mì they held no gluten. On Tuesday three governance forms were cutting every answer off at one character, and nobody filling one in would have been told why. On Wednesday calls in Chrome were telling people they had refused a permission nobody had asked for. On Thursday a moderator could clear a channel they could not hear, and on Saturday re-importing NeuroHome would have deleted a guest’s door, and both times nothing would have said so. None of these faults was new. Four came out only because something new needed them: a manual that had to name every control, a food truck, a new power on the CB, and a guest’s room. Most of this week’s cost was paid on work we had already called done.

The week’s longest-running job was quiet in the same way. Our EspoCRM trial spent more than a day taking in the team mailbox, and none of it made a commit, so none of it reached this log or the running changelog until the weekly post went looking. A fault nobody hears about and a day of work nobody logs get found the same way: by somebody reading back on purpose.

Sunday — 2026-10-04

Accomplishments

Four rooms and a manual on Stimpunks.World in one Sunday, and two of the pieces had to wait on the world outside. YouTube’s channel feeds answered 404 for every channel for several hours overnight, so the first fill of Hey, Good Cookin’’s teaching screen waited until they came back. FoodSafety.gov refuses a script, so its cooking temperatures were read in a browser by hand. And Brew and Stew went up with one of Ryan’s ten videos held rather than shown, because it looked like a re-upload of another, and that call is his and not a generator’s.

Insights and Takeaways

A cut-off search result reads exactly like a complete one. Renaming "Forget Me" to match the Profile button’s "Forget me" took two commits, because the first one’s search output was truncated before it reached the three shelter rooms, and nothing in the output said so. The same day turned up a control that only worked one way: Move on the CB did nothing visible when pressed rather than dragged, and the only description of its arrows was for a screen reader. Neither showed up until somebody wrote a guide that had to name every control and say what it does. Writing the manual was the test.
The catch-up that writes this entry cannot see a day’s work that never touches git. Drafting the Week 40 changelog found that Friday’s move from Notion and HubSpot to EspoCRM (contacts, grant requests, a plugin replacing Zapier, the team’s documents) had left one line in the running file, because it happened in a workspace with no commits for this check to read. The day sections caught it only because a thin day looked thin. The same draft left something open: our mirror of Stimpunks.World is 25 pages behind the live site, so its links had to be checked against the live sitemap instead, and that will hold until the mirror is re-synced.

Gratitude

Kaya Oldaker, whose Autism Infinity Dragon is now credited as public domain, the way she released it, on /together/, /front/ and /about/testimonials/.

Monday — 2026-10-05

Accomplishments

Five new places on Stimpunks.World in one Monday: four outdoor lots and a pub. Most of the cost was in what the shared tools got wrong when a new room met them. The kitchens’ allergen engine had been telling three bánh mì they had no gluten, because it did not know a baguette is wheat. Big Steep’s list of words that pressure somebody to drink refused A Quiet Pint’s round tables, so "round" had to be narrowed to the round somebody buys. NHK’s RAMEN JAPAN had embedding turned off, which only came out because every film was checked on its own watch page before it went on a rack. Small screens and print got new section numbers twice in one day, and both times every place that names them had to be found and changed.
Our EspoCRM trial learned to send, and gained a connection for AI assistants that cannot delete anything. EspoCRM’s support had switched on sending and the assistant connection for our cloud instance, at our request. Our team address now sends through Gmail using the account’s existing Google sign-in, so no password was typed or stored, and Ryan’s test email arrived. The assistant connection can find, read, create, and update the records we use, and it cannot delete, export, bulk-edit, or send an email. Ryan created its key himself, so the key never passed through Claude.

Insights and Takeaways

A shared check is written for the rooms that already exist, and each new room is the first real test of it. The allergen engine and the drink-pressure sweep were both right for every room before Monday, and both were wrong the first time a food truck and a pub used them. The fix landed only partway: the pub’s sweep now looks for an excusing word next to the word it excuses, and the other rooms’ sweeps do not yet. That is still open. Where the sources disagreed, the Pile says so instead of picking one, because two Wikipedia articles give different years for Emdrup’s junk playground.
The assistant connection failed three times on the way in, and two of the three failures were ours. The setup command we gave Ryan had no scope, so it saved the connection only for the folder he ran it in, and a second session found it missing. Then Claude Code turned out to be too old for the protocol version EspoCRM speaks, which an upgrade fixed. Then EspoCRM refused the tool list itself: 14 of the 48 tools we had defined asked for fields it will not hand over that way, such as attachments and a contact’s full name, which is built from parts. EspoCRM had taken all 48 without complaint and refused them only when a real client asked. A configuration nobody has used yet is still a draft, which is what Tuesday’s forms showed again the next day.

Gratitude

Jim Butcher, whose McAnally’s in the Dresden Files gave A Quiet Pint its thirteen of everything and its asymmetry.

Tuesday — 2026-10-06

Accomplishments

Rolls for the pub’s player piano on Stimpunks.World, and most of the day went on telling a real piano roll from something that only sat next to the words. Every roll was chosen from its Commons description, which says what roll it is and what played it. Several files near "piano roll" were notation software playing sheet music, and some real rolls were of songs whose writers died too recently for public domain everywhere, so both were left off. The checks were broken on purpose first, and all ten faults were caught, before anything was trusted. The drawn piano gained a roll in its window, so the share card had to be redrawn too.
Every free-text field on three live governance forms had been capped at one character, and nobody filling one in would have been told why. The Conflict of Interest Statement (17 fields), the Board Member Agreement (5) and the Volunteer Agreement (6) were all affected. We fixed them with one WPVibe edit per form, each removing the setting and each replacing exactly as many as predicted: 17, 5 and 6. The public Volunteer page now renders all 33 fields with no length limit, against 6 held to one character before. Then the three build scripts were fixed, so the next import does not bring it back.

Insights and Takeaways

"Off" written as an empty value was read as "on," because the form builder only asks whether the setting exists. Our build scripts wrote the length limit as present-but-blank on every text field, meaning off. WPForms tests only whether the key is there, so it showed Limit Length as on, and the first save in the builder wrote a limit of one. Nothing in the import JSON looked wrong. The fault only showed on the rendered page, as maxlength="1". The fix is to leave the key out, which is what the builder itself saves for an unchecked toggle: match what the tool writes, not what seems to mean the same thing.
A file’s name is not its description. On Commons, "piano roll" sat beside recordings that were never a roll at all, only software reading notation aloud. The only reliable test was the description on each file’s own page, saying what roll it is and what played it, and the pub now repeats only what those pages say.

Gratitude

Scott Joplin and Alexander Scriabin, who played two of the pub’s rolls onto the paper themselves, in 1916 and 1910, and the Wikimedia Commons contributors who recorded and described them.

Wednesday — 2026-10-07

Accomplishments

We answered "people are having a hard time connecting" on Stimpunks.World, and the answer cost a promise. Who’s online only works because it reverses two rules Ryan had made and written down. One was the CB’s refusal to show a list of who’s around. The other was Be seen here meaning "only the people in my room can see me". Everyone who pressed that switch before Wednesday agreed to less than it now does. We could not ask them again, so the privacy page says what changed and the date it changed, and switching it off takes a person off the list at once. A narrower first attempt, built for Helen Edgar’s ask to find someone by name, lasted 35 minutes before the broader one replaced it.
Publishing Brand Voice meant correcting a live page on the way out. The Punctuation page of our own Style Guide told writers to put no spaces around em-dashes. That contradicted the page’s own example, its own earlier rule, and 3,595 spaced dashes in our posts since July against 1 unspaced. The new page sits below the Style Guide and defers to it, so if we had left that line alone, Brand Voice would have deferred to an error. One surgical edit fixed it, with a revision kept. Still open from the same day: the curly-quote fault after links, 36 of them on 20 earlier pages, untouched.
Our EspoCRM trial began taking in the team mailbox’s history, and the first check was that nothing could write back to anybody. Sending had been live since Monday, so an auto-reply to years of old mail would have gone out to real people. Before anything ran, auto-reply, case creation, and email notifications were confirmed off on every account. The import took six temporary accounts, because an EspoCRM account remembers how far it has fetched and that marker cannot be moved back. Five copied our pipeline label accounts, and the sixth read a Gmail label Ryan put on all our mail from before 17 September. By that night, 3,633 old emails had landed in their pipeline folders.

Insights and Takeaways

One rule we had written down for Stimpunks.World had been impossible from the day we wrote it. The 2026-09-28 rule said our pages would get no camera, microphone or screen permission while the call inside them did. Browsers do not work that way, so every call in Chrome silently failed, and told people they had refused something nobody had asked them for. The promise behind the rule was right: no page of ours asks for any of the three. It was being kept in the wrong place. It now lives in a build check that reads every script we serve. A promise enforced by a mechanism that cannot do the job is only a sentence, and a reader cannot tell it from one that is kept.
The mirror nearly made us propose an edit to a list that maintains itself. Brand Voice went up under About, and the About page in our site/ mirror showed an "Administrivia" list of child pages without it. A session read that list as hand-typed and offered to add the new page. The live page already listed it, because the list is generated when the page loads. A rendered list looks exactly the same in the mirror whether someone typed it or a block built it. Even checking the live page was not enough at first: a plain fetch ten minutes after publishing still served the old list from the edge cache. Only a cache-busting fetch showed the truth. /about/ is now the second standing example in our working notes, alongside /why/.
The archive import ran in the opposite order from the one we had announced. We said it would bring old mail in oldest first. Ten minutes later it was plainly going newest first, because Gmail numbers messages in the order a label was applied, not the order they arrived. That sent it into months the Mutual Aid import had not reached yet, where it could have filed requests in the archive instead of their pipeline folder. We paused it after 64 emails, for that and to check the whole archive would fit our plan, moved those 64 back out, and saved their IDs. A check soon after it started caught it, not anything the import reported.

Gratitude

Helen Edgar, whose ask for a way to find somebody by name started what became Who’s online, and everybody who told us they were having a hard time finding each other.

Thursday — 2026-10-08

Accomplishments

Four videos on one Stimpunks.World screen took four separate checks and a test run before any went up. For each one we opened its watch page and confirmed it was public, allowed to play inside another site, not age-restricted and not live, and we measured its runtime. Then we played all four inside a frame on a test copy, because a video that passes every check on paper can still refuse to play there. A screen also made one of the room’s own sentences false. Nothing in it moves became nothing in it moves by itself, and that line had to change the same day the screen arrived.
By lunchtime our EspoCRM trial held the team mailbox back to October 2021, about 16,700 emails in all. The pipeline folders took 3,633 and the archive 13,195, with 870 attachments. The archive came in at about eight emails a minute, because EspoCloud fetches 50 messages a run and locks that setting, so it took about fourteen hours, checked every two. No auto-replies went out and no cases were created. Then the six temporary accounts were deleted.

Insights and Takeaways

Giving people a new power on the CB showed us an old check had never been there. To let anyone take their own message off the air, we had to state exactly whose a message is. Writing that rule down meant reading the moderation step closely, and it had never asked whether a moderator could hear the channel at all. Someone could have taken messages off a channel they had no way into, and nothing would have said so. The gap was older than the feature and only showed up because the feature needed the rule spelled out.
Every email EspoCRM could not match to a sender landed on one contact: 10,103 of them. A contact called Stimpunks Team had come over from HubSpot carrying our own team address, and EspoCRM files any email it cannot match to a sender under it. Newsletters, receipts, and auto-replies from five years of mail all ended up on the record that stands for us. The emails are fine. Whether that contact should exist at all was left for Ryan to decide.

Gratitude

The people who make EspoCRM, an open source CRM that now holds our team’s mail back to October 2021, each message linked to its contact wherever the address matched.

Friday — 2026-10-09

Accomplishments

Nothing was recorded on Friday. The only commits were the morning timers refilling the street’s racks, no working session ran, and nothing was published.

Insights and Takeaways

Gratitude

Saturday — 2026-10-10

Accomplishments

Another guest built a room on Stimpunks.World through Your Room, and we kept it hers. Kristina Brooke’s Words, Bud, Beats changed by one line on its way in, and only because a room’s script may not spell out its own address. The TIDAL players she asked for went on in her Copy button’s clothes, under her own links, and the notes say plainly which parts Stimpunks added.

Insights and Takeaways

When a guest’s room is refused, check the importer before the room. Words, Bud, Beats was refused twice for faults that were ours: the importer read our own prompt’s "- none" as a song called none, and told her a property she had declared was undeclared, with a reason that was untrue. A third fault would have deleted her door the next time anyone re-imported NeuroHome, and nothing would have said so. The tool sits between a guest and the street, so its mistakes land on the guest as a refusal of their work. We fixed each one and then broke it on purpose, to prove the refusals that should still fire still do.
Both of Saturday’s stimpunks.org posts ended by turning the check on ourselves. The reflection audit that should have stopped the Week 40 post had passed eleven placeholders, and the Campfire Synthesis closed by refusing to let a Neurodivergent organization use Black life as a metaphor for neurodivergence. Neither was caught by a gate; both were caught by reading. What the day leaves open is the same gap the Week 40 post described: this week’s Friday reflection is empty again, for work that happened outside any repository a timer can see.

Gratitude

Kristina Brooke, for sending Words, Bud, Beats through Your Room, and for asking for TIDAL players, which every future guest room can now carry.

Looking Back

Meaningful Moments

Kristina Brooke’s room. Last week this reflection said it was looking forward to the second room somebody builds for themselves. On Saturday it arrived: six records on a shelf at desert dusk, each pairing a few of her words with one song and one strain.

Robin Wall Kimmerer, reading her own book. Ryan found the authorised audiobook preview, narrated by Kimmerer, and Swaying Sweetgrass now opens Braiding Sweetgrass in her voice.

Life is Teaching Me

Being used once is not being tested.

Last week we expected the next guest room to come through a tool that had already met a real person, and it did. It still found three faults, none of them the ones NeuroHome found. The food trucks found what the kitchens had not. Each new arrival tests the part that nothing before it touched, so a tool that has worked once has only been tested as far as that once.

Habit Insights

Last week’s one change did not get made. The Week 40 reflection asked us to write the reflection on the day for work that leaves no commit, and it named the EspoCRM move. This week that move did three days of work: sending and an assistant connection on Monday, and the mailbox import across Wednesday and Thursday. None of it was written down on the day, here or in the running changelog. The EspoCRM entries above were written on 17 October, from the session’s own record. They keep the facts and lose what the days were like, which is the trade that change was meant to stop. A resolution is a promise kept in the wrong place, and Wednesday’s entry above says what those are worth.

And this time the empty-day check could not have helped. In Week 40 the hole was a blank Friday, and a thin day looked thin. This week Monday, Wednesday, and Thursday each already held entries about other work, so none of them looked thin, and a day-long import was missing from two of them anyway. The check counts empty days. It cannot count missing work. Saturday’s entry, written by the morning catch-up, guessed that Friday held work no timer could see. That was the Week 40 lesson applied to the wrong day. As far as any record shows, Friday was quiet, and the unseen work this week was on the days that were not empty.

Looking Forward

One Change I Can Make Next Week

Teach the morning catch-up to read session records, not only commits. Our EspoCRM work left a full session record on disk every day it happened, and the catch-up never opened one, because it only reads repositories. A day with a working session and no commit is exactly the day that needs writing up, and the catch-up could say so the next morning instead of a week later. That moves the promise out of a resolution and into something that runs.

I’m Looking Forward To

Sunday’s Campfire, where Maya Angelou and James Baldwin speak in their own voices in a room we have been quoting them in for years.