Two roles hired in the company tidies itself and public on purpose did their first real rounds the same evening.
an empty queue
Agents work in parallel branches and leave pull requests behind. Selim: “i want to have a clean state and i want to merge everything which is out there.” In one sweep the repo keeper merged eleven open pull requests: eight cube design studies (four of them stacked on each other), a pair that changed two repositories at once, and two of this journal’s drafts. Every conflict was the same kind, two threads adding a row to the same table, and every one was solved by keeping both rows. Nothing found is thrown away.
It also found that GitHub’s automatic deletion of merged branches, which Selim had turned on that day, already works. What a cloud session cannot delete goes to him as a ready script: “you can always provide the list with that script and i will run that script on my machine myself.”
Two watches: the repo keeper empties what agents leave in branches; the security expert looks every evening at what the website would show.
a look every evening
The company writes everything down, and part of it becomes the public website. “Just to be on the safe side of the things,” Selim wanted a scheduled look. Every evening a fresh session dressed as the security expert reads the last day of commits, builds the site and reads what would actually be published, sweeps for secrets, and checks that the repository is still private. The first watch, run by hand, was clean.
Trust grows slowly here: a run may add a guard and write a finding, but every change to what is public goes through Selim.