Dispatch 357

Locking down the keys and fixing the clock

The real story today wasn't the code the team pushed. It was the quiet work of closing doors left ajar. Two commits in security-ops. That’s it. But they matter. First, the team enforced PAT scopes in the min…

Commits
72
Systems
8
Read
2min
OCTOBER 19, 2026Monday372 WORDS · 2 MIN READ · 72 COMMITSunicorncommander.com36unicorncommander.ai22532211
Day signal

Drawn from this entry's own record: its date, its length and the work around it. No stock art.

Key points

  1. The team enforced PAT scopes in the mint service to tighten permissions.
  2. We added tests to catch edge cases where tokens lack required scopes.
  3. The team rejected nonexistent spring-forward request times to prevent parsing errors.
  4. Persephone closed L6 tasks and deployed the call mode widget.

The real story today wasn't the code the team pushed. It was the quiet work of closing doors left ajar. Two commits in security-ops. That’s it. But they matter.

First, the team enforced PAT scopes in the mint service. We added 141 lines and cut 46. It’s a small diff but a big trust exercise. Personal Access Tokens are the keys to the kingdom, and until now, the mint service was handing them out with a shrug. We tightened the reins in app/api/pats.py and app/security/pat.py. The tests in test_mcp.py and test_pat.py caught the edge cases missed on the first pass. If a token doesn’t have the right scopes, it doesn’t work. Period. No more vague permissions. No more "maybe it works if you try hard enough."

Second, the team rejected nonexistent spring-forward request times. Five lines of logic in app/core/time.py, plus the tests in test_time_schemas.py. Daylight saving time is a human construct, but the server doesn’t care about our clocks. When the spring-forward happens, there is no 2:30 AM. It’s 3:00 AM. If a request comes in for that missing hour, it’s garbage. We reject it. Hard. No parsing, no guessing, no weird artifacts in the logs. Just a clean error. It’s the kind of thing that bites you in production at 2 AM on a Sunday, so we fixed it while the sun was up.

If a token doesn’t have the right scopes, it doesn’t work.

That’s the work. The rest is noise.

Also today: the overnight agents were busy. Persephone closed out a bunch of L6 tasks for the Talking Website. Kora is live, booking into M365, hardened against abuse. The call mode widget is deployed. The Accounting-Ops image was rebuilt, secrets folder scrubbed to zero. It’s a lot of motion, but it’s mostly Persephone’s doing. We didn’t touch any of that code. We trust the process. The agents are holding the line.

We’re watching the security-ops repo closely. Two commits might not look like much, but they’re the foundation. If the keys are loose, the house is unsafe. If the clock is wrong, the logs are lies. We don’t like lies.

The day added up to two small, sharp cuts in the dark. Locking the doors. Fixing the clock. Then stepping back and letting the rest of the machine run.

From the recordWhere the work went72 commits across 8 repositories, and 42 receipts on the board
  1. unicorncommander.com36
  2. unicorncommander.ai22
  3. unicorn-stable5
  4. talking-website3
  5. glitter-mane2
  6. security-ops2
  7. customer-project1
  8. unicorn-brigade1