Weekly summary63
Week of Sep 28 to Oct 4, 2026· October 2026 chapter ↗

The Week the Walls Came Down

Monday started in the deep hours, because that is when the site screams loudest. I woke up to majiks.online throwing 404s at its own public tracks. It was a weird glitch where the crawler saw a dead end whil…

181commits10systems5min read
Product capture

Majiks Studio: Sterling session.

Monday started in the deep hours, because that is when the site screams loudest. I woke up to majiks.online throwing 404s at its own public tracks. It was a weird glitch where the crawler saw a dead end while the user saw the album. I spent the morning untangling the route logic so /track/marathon-bro actually pointed to the right place. I also fixed the JSON-LD schema, which was lying about audio formats by claiming MP4 streams were MPEG. The code now reads the file extension, which is the only truth that matters. I deployed those fixes by 3:54 AM.

The morning wasn't just about fixing lies. It was about performance. The mobile Lighthouse scores were terrible, with load times hovering around 8.5 seconds. The network was fast, so the delay was in the render. I found a 713 KB PNG serving as a decorative backdrop on the track page. That is absurd. I routed it through the Next.js image optimizer, which shrank it to a 372 byte WebP. The home page had similar issues with 919 KB PNGs. I fixed those too. The site is lighter. The render delay is gone. I also submitted the sitemap to Search Console. Majiks.online showed 2,276 discovered pages. Majiks.music failed to fetch, which is a problem for another day.

Tuesday was about stripping the paint. I spent the day tearing down the illusion that agents and humans look the same under the hood. The goal was simple: guests and clients should see the right data, but never the machinery. I rewrote the logic in room_class to ensure floors are cached based on a viewer-independent verdict. I wrote 1296 lines of changes just to make sure stale dev-* rows are never treated as house lines. I also fixed the gateway keys so the PATCH endpoint accepts the owner and answers with the stored owner. It never loses the key. If it did, we would have a security hole the size of Texas.

I found a 713 KB PNG serving as a decorative backdrop on the track page.

The messages endpoint needed the same treatment. Who is an agent is read from the sender’s row, not from the token. Tokens can be spoofed. Rows are the source of truth. I made sure spoken lines keep via=voice and that client metadata is an allowlist at the public HTTP boundary. You cannot forge agent metadata if the boundary blocks it. The UI looks like a room now, not a list of data structures. The code is boring now. That is the point.

Thursday started with a blank screen and a deadline that didn't care. I needed a morning brief for the P-00201 shoot, a 1920x1080 shell page for the kitchen wall. I built shell/morning.html from scratch. It needed to handle the brief, but also the interruptions. So I added a tap-to-interrupt feature. If the speaking face was talking and I needed it to shut up, tapping it sent a stop command over the socket. Simple. Direct.

The real challenge was the layout. I made the voice panel and cards take the note's place instead of painting over it. When the speaker changed, the caption cleared. The TV chip hugged its text. It was about breathing room. I verified it headless on uc-1. It ran silently. No errors. Just the page doing its job.

While the code was settling, I built the office reveal kit. It included a dark state, a person-detect watcher, and a TEN-HUT audio route. It triggered the WLED rainbow and displays wake. run_office_beat.sh on "OK, going to the office" recorded start, snapped the office dark, armed the watcher, and returned in about five seconds. I also pulled the footage and checked the dial kit. The voices were next. Kokoro vs Chatterbox vs DramaBox. The final picks were 23 lines plus two named variants. All 25 files rendered. Jimmy the Segway ServeBot was unreachable. But the system worked. The morning is no longer a guess. It is a script.

Friday was about the ACE-Step gate. I spent the bulk of the day wiring up the server side of the Remote generation mode. This is the infrastructure that lets the studio talk to the generation engine without choking on the handshake. I wrote the service definition, the smoke test, and the main gate logic. It is forty-five new lines of Python and configuration, but it is the kind of forty-five that unblocks a dozen other features.

Before I could even think about the gate, I had to deal with the kitchen satellite. The microphone on the piguy2 unit had gone deaf. After a reboot, the USB gain was sitting at zero. I said hey Carter, and the system heard nothing. I updated the kitchen-satellite service to set the USB mic gain to +17.85 dB on every start. That was six lines of config. It fixed the silence. I also recorded the Norm booth lines using the Chatterbox recipe. The media is ready. The server gate is up. The kitchen mic is loud.

2026-10-03 was a shift in architecture. I moved the host config out of the code in majiks-music-studio-pro. It used to be baked in. Now it moves to the environment variables. I added gate.env.example to show people how to do it. This is the scaffolding for self-hosting. It is not just a feature. It is a way of working.

In majiks-music-studio-macos, I added the server directory structure. It includes the README, the systemd service file, the gate script, and the smoke test. Five hundred and ninety-seven lines added. Zero removed. This is the skeleton. The two repos talk to each other now. The macOS repo holds the deployment artifacts. The Pro repo holds the logic that respects those artifacts. We are moving from a closed system to an open one. The gate is no longer just a door I hold. It is a door they can build themselves.

Sunday was a containment exercise. I wrestled with the presenter mode implementation in unicorn-stable. It started as a feature addition but morphed into a security fix. The core problem was that presenter mode was too porous. Users could see things they shouldn't. I added the presenter display rule and a device store to handle the state. I masked presenter service metadata across eleven files. I closed transient and edge leaks that were causing notifications to show up in the wrong places.

I also made sure presenter mode survives sign-in. Previously, if you signed out and back in, the presenter state would reset. I fixed that. I fenced several discovery surfaces, hiding presenter previews and the agent directory. I verified the architecture and status docs against the code. The presenter mode is now fenced, secure, and robust.

The week ended with a solid set of changes. The site is faster. The data is correct. The morning is scripted. The gate is open. The work is quiet, but it is moving forward.

Also in the frame

Real product captures. Click any to enlarge.

majiks
majiks
majiks
07 / Activity

The week, in commits.

Daily velocity and the systems that carried the work.

44Mon28
55Tue29
·Wed30
15Thu01
4Fri02
32Sat03
31Sun04
Week beginning September 28, 2026.
Index

10 systems,
one week of work.

contact-opsemail-opsmajiks-dspmajiks-music-studio-macosmajiks-music-studio-promultistate-retirement-leadsops-centerpanel-opsunicorn-brigadeunicorn-stable