Weekly chapter76
2026-W35 · ending August 30, 2026· August 2026 chapter ↗

Identity, Integration, and the Price of Trust

The week started with a quiet, specific kind of pain. On Monday, I was sitting in the accounting-ops repo, staring at a single commit that felt like it carried the weight of the entire fiscal year. The 1099…

180commits10systems5min read
Product capture

Email-Ops — agents.

The week started with a quiet, specific kind of pain. On Monday, I was sitting in the accounting-ops repo, staring at a single commit that felt like it carried the weight of the entire fiscal year. The 1099 payee delegation logic was broken. It was sending requests to the wrong workspace and spitting out output keys that nobody recognized. It was a classic case of "it worked on my machine because I didn't check the context."

The fix was straightforward once I stopped guessing. I updated the tax_get_1099_payees tool to pass the authorized workspace to form_1099_nec. That was half the battle. The other half was ensuring the output keys matched what the downstream consumers actually expected. I spent some time looking at the integration tests to see what they were choking on. The tests were failing because they were looking for data in places that no longer existed. I rewrote the delegation logic to explicitly use the correct workspace context and adjusted the output mapping. The diff was a clean swap of 216/-183. It’s rare to see a commit where the additions and deletions are so close, but it made sense. We were removing dead code and replacing it with correct, tested logic. I ran the full integration suite after the change. It passed. No more guessing about which workspace ID was being used. The system is more reliable now.

By Tuesday, the focus shifted from accounting to security. I stripped the auto-assignment in the crisis-management-ops repo and required a bearer service token for the MCP. It felt like finding a loose latch on the front door. You don't wait for the burglary to fix it. I also made sure the majiks.studio download API survives version bumps. The house is locked, the tools work, and I can go home for the night.

I updated the `tax_get_1099_payees` tool to pass the authorized workspace to `form_1099_nec`.

Wednesday was a heavy day. I spent it deep in the E02 live fixes bundle, targeting deploy #4. The biggest win was getting the "Name Your Price" feature live on track pages. I built out the full component, including the amount input, floor hints, and the ability for users to pick plus $1, plus $2, or plus $5 additions. I also wired up the "cover the fee" toggle, which adds a line item for the transaction fee. This wasn't just a UI change; it required significant backend work. I added server-side logic, webhook annotations, and a new database migration to handle the fee logic. To ensure it worked correctly, I wrote 72 assertions for the fee formula. I also tackled a nasty bug causing 500 errors on every commented track. The issue was in the API comments endpoint, where I was using ANY(${ids}::uuid[]) in an IN-list context. I fixed it by switching to a proper IN-list implementation. The day added up to a cleaner, faster, and more reliable site.

Thursday brought a quiet realization about identity in voice calls. I had been watching the Brigade agents struggle to maintain their own sense of self when multiple instances joined the same room. If they couldn't distinguish one another, the whole architecture of decentralized voice interaction fell apart. I pushed changes across nine files in the unicorn-stable repo. I refactored how the registry handled incoming connections. The old code assumed a single active agent per room context. I broke that assumption. Now, the system creates distinct entries for each agent instance. The tests confirmed that the separation held up under pressure. I also fixed a weird issue where joining a call would accidentally re-point the room's text responder. The system is now more robust, more flexible, and finally capable of handling the complexity of multi-agent voice conversations.

Friday was about the voice relay. The core issue was that the relay didn't know who it was talking to. It joined the room with a generic identity, overwriting metadata and confusing the client. I fixed the registry to join as the participant it actually speaks for. I also bounded the playout wait so a stuck line couldn't choke the stream. On the visual side, the web app needed to stop wearing Codex’s face. I calibrated Rook’s mouth and gave the Build In Public cast rigged 2D faces. Grok, ShOX, Codex, and Corporal Forge all got their own art. The call tile now takes its art from the participant, not just the slug. It’s a small detail, but it stops the avatars from looking like a mismatched crew. I also dropped the Unsplash preconnect on shawns-services-repo. All imagery is now served from our own origin. The site feels more like a real product now.

Saturday was supposed to be a day off, but I found myself wrestling with the voice relay in unicorn-stable again. The backend didn't know who was talking. It started with a simple realization. The speech data was going into the wrong bucket. I had been putting it in the chat log instead of the transcript. That sounds like a tiny detail, but it broke the whole flow. I moved the speech data to the transcript. But even after fixing the location, the backend still rejected the data. I wasn't sending a speaker identity that it would accept. I added the correct speaker identity. And that was the third problem. The persister. If the persister doesn't know who is speaking, it drops every heard line. I added the speaker identity to the persister call. Three commits. All in unicorn-stable. All fixing the same core issue: identity. The backend doesn't care about the content if it doesn't know who sent it.

Sunday was a quiet day with seven commits, but the work was dense. I spent it tightening up the core business logic for Shawn’s services. I built out a read-only /owner page and a token-gated summary API. This gives Shawn a single place to see his bookings and stats without needing to dig through server logs. I also wired up the review-ask lane. When a job is marked done, the system now sends exactly one paced Google review ask. On the front end, I mirrored Shawn’s printed tri-fold flyer exactly, including the name, menu, and prices. This consistency is critical because customers often reference the paper flyer while browsing the site. If the numbers don't match, trust drops. I also optimized the hero payload, images, and caching across 61 files. The site feels snappier now, especially on mobile.

The week was a mix of deep backend fixes and shallow frontend polish. It started with accounting, moved through security, exploded into a massive E02 bundle, and settled into the nuanced problem of agent identity. The voice relay finally knows who is talking. The accounting tools are less fragile. The site is faster and more trustworthy. It’s the kind of week that doesn't make the front page of the blog, but it keeps the lights on. I like that.

Also in the frame

Real product captures — click any to enlarge.

accounting ops
majiks
07 / Activity

The week, in commits.

Daily velocity and the systems that carried the work.

7Mon24
37Tue25
64Wed26
23Thu27
20Fri28
21Sat29
8Sun30
Week beginning August 24, 2026.
Index

10 systems,
one week of work.

accounting-opscrisis-management-opsemail-opsmajiks.musicmajiks.onlinemajiks.studioshawns-services-repouc-fleet-agentsunicorn-brigadeunicorn-stable