Notable verbatim quotes

Tags: thesis, continuous-ai Section 4 (lines ~35–50) "There's a third pillar to that. There's actually three. It's not cicd. It's CI, CD and continuous AI, CAI."

Tags: continuous-ai, characteristics Section 4 "So these are automatable. They're repetitive, collaborative, integrated, audible. They're, and crucially, there are lots and lots of variants of these things."

Tags: continuous-ai, vs-individual-productivity Section 4 "there are event triggered, they're proactive, and it's about collaboration, team productivity, not just individual productivity."

Tags: polarity, framing Section 3 "I think the industry in their right, rightful pursuit of individual productivity has maybe not been focusing on automation and not being focusing on continuity. And at the heart of GitHub is, of course, continuity."

Tags: individual-productivity, crunch-point Section 4 "the individual becomes a bit of a kind of crunch point for all the information flows going through a software project."

Tags: morning-routine, repolaris Section 4 / 9 "start my day with code that's better provided by my continuous improvement processes."

Tags: github-agentic-workflows, definition Section 5 "effectively it takes a specification of an agentic workflow and hardens it into a GitHub Action. I don't mean compiler. I mean, it's got a prompt and it wraps that ... it's mainly about hardening it in security sense to make sure you can trust the flow that's being implemented by that agenda workflow."

Tags: repository-as-factory Section 5 "turning every repository into a software factory, just like cicd automated your build and, and deployments so we can automate a huge range of subjective activities in the repository."

Tags: github-actions, democratisation Section 5 "when a company adopts GitHub Actions, what they're actually doing is giving a playground, an automation playground where developers can claim, can make and use cloud resources ... You don't have to go and ask ... You just claim them through GitHub Actions."

Tags: workflow-file, anatomy Section 6 "Front matter plus markdown. You check it in, you harden it to a yaml, it runs. That's it. You have the factory."

Tags: safe-outputs, safety Section 6 "They run read only with no access to secret, no direct access to secrets they run in a container. And they have an extremely narrow output channel. In this case, it's allowed to create one issue."

Tags: plan-apply, threat-detection Section 6 "It's a bit like a plan apply kind of thing. And the apply is not done gently. It's not done through MCPs. It's done as a secondary stage and actually threat detection in between those stages."

Tags: prompting, ambiguity Section 6 "it's got some prompting or sort of natural language programming, usually very sort of deliberately ambiguous, generally useful ambiguity."

Tags: human-in-the-loop Section 6 "They don't ever merge pull requests. The pull request is a kind of hard point that it's always the human in the loop."

Tags: safety, inversion Section 7 "In automation, it's actually the opposite way around. It's like a rail track. The better the quality of the rails that you're on, the faster your train can go, the more you can automate."

Tags: safety, mandate Section 7 "Do not run coding agents directly in GitHub Actions or any other CICD thing. Without a security architecture of some kind."

Tags: agent-zoo, pelle Section 8 "he has taken the philosophy of let's create a new agentic automated workflow just about everything. And it's created hundreds and hundreds of these things."

Tags: semantic-refactoring, evidence Section 8 "in this use of semantic function refactoring, the workflow had 112 merge VRs at 142."

Tags: repolaris, definition Section 9 "Repolaris is one particular agentic workflow ... It reads its memory. And then chooses a couple of the smallest board of tasks ... once a day or at some appropriate kind of cadence, it's going to wake up and it's going to do these things in the repository."

Tags: maintainer-joy, repolaris Section 9 "Turn on Repolaris. And I actually started to enjoy being a maintainer again."

Tags: dormancy, forward-velocity Section 9 "We're totally backlogged into forward progress. They're turning dormancy into forward velocity."

Tags: factory-thinking, repository Section 10 "when I think of a repository now, this is what I think of it as a site where humans and agents come together to work collaboratively to get forward velocity"

Tags: human-gate Section 10 "you can gate the factory on human and organizational needs ... Humans are absolutely part of this process and the human needs are paramount throughout what we're building."

Tags: process-engineering Section 10 "Go read books and the kind of chemical industry or the mechanical engineering kind of industry ... we now have to take that kind of thinking and bring it into the software development process."

Tags: quality-gate, sub-factory Section 12 "my factory is not flowing at the moment. It's like we haven't got a sufficient quality gate ... The key thing step is to step back and take let out a quality date to the factory."

Tags: closing, work-not-fixed Section 13 "work is not a fixed amount of work to be done. There's a huge amount of work that needed to be done that was simply not being done because it was labor constraining too expensive."

Tags: closing, vision Section 13 "The car, the automobile led to travel that wasn't being done before. The factory led to millions of quality products that weren't being done before. Medicine led to diseases being treated that weren't being treated before."